Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Units and scales (and currency) in Table Schema

See original GitHub issue

STATUS:

We had a Units spec - see #35 - which then got moved out but we’re moving back in see https://github.com/frictionlessdata/specs/issues/537
We then can reference this from Table Schema - this issue here

Excellent discussion with @dr-shorthair today led me to consider importance of units and scales (and currency) in JSON Table Schema.

Suggest we could specific at MAY level:

unit: simple-string-descriptor e.g. m/s
unitSemantic: pointer-to-a-url-describing that unit - could be RDF uri
currency:      # could be part of units but think probably better separate
factor: a scaling factor (e.g. 1000 would mean to scale by 1000

References

QUDT - http://www.qudt.org/ - quantity, unit, dimensions and types -
Unified code of units of measure - http://unitsofmeasure.org/
Data Protocol on Units - http://dataprotocols.org/units/

Issue Analytics

State:
Created 8 years ago
Reactions:2
Comments:30 (21 by maintainers)

Top GitHub Comments

2reactions

yohanbonifacecommented, Dec 19, 2022

Hey, is there still interest in this feature ? We (for French administration) would use it (basically, tools consuming table schema would infer some behavior according to the unit, when defined). Any way we could help it land in the spec ?

2reactions

rgiesekecommented, Jun 12, 2017

How about something like