Skip to content
This repository was archived by the owner on Apr 23, 2021. It is now read-only.
This repository was archived by the owner on Apr 23, 2021. It is now read-only.

Units should be defined explicitly #127

Description

@stefanoborini

After the discussion about units, it is probably important to remember the following: data models generally do not focus on implementing every possible option. What they do is instead choose one standard unit for internal storage, and use that.

Meaning: we don't need a unit ontology, or to express e.g. MASS as an entity that has both a value and a unit. We just need to say that MASS is a value of mass in kilograms. If we want a different unit, it is generally because it is relevant to a specific field (e.g. mass in atomic units is called atomic mass unit and values are expressed as such, e.g. 13 amu)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions