Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document measurement types #396

Open
mbjones opened this issue Jun 2, 2023 · 0 comments
Open

Document measurement types #396

mbjones opened this issue Jun 2, 2023 · 0 comments

Comments

@mbjones
Copy link
Member

mbjones commented Jun 2, 2023

EML's concept of measurement types and the Steven's typology is not always familiar. A simple flow chart could help explain the choices and give examples, such as:

flowchart TD
    A(Variable X) --> B{Values naturally ordered?}
    B --> |Ordered| C{"Equal magnitudes between values?
    (6 - 5 == 11 - 10)"}
    C -->|Equal - Quantities| D{Represents date or time?}
    B -->|Unordered| F("fa:fa-car Nominal
    Left /  Right")
    C -->|Unequal| G("fa:fa-car Ordinal
    Low / Medium / High")
    D -->|Yes| H("fa:fa-car DateTime
    2023-05-13T14:32:11Z")
    D -->|No| I{Has meaningful zero?}
    I -->|Not Meaningful| J("fa:fa-car Interval
    40 C")
    I -->|Meaningful| K("fa:fa-car Ratio
    12.2 m")

Feedback welcomed on this representation, and better ways of explaining each. In EML we mainly use this to differentiate what kind of attribute metadata is needed to describe the variable, so the interval/ratio distinction isn't really needed. But otherwise, for the rest of them they result in different metadata needs. Should we add something like this to the documentation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant