(Proposal 3, modified)
- value (xsd:double or xsd:decimal)
- unit (a wikidata item)
- totalDigits (xsd:smallint)
- fractionDigits (xsd:smallint)
- originalUnit (a wikidata item)
- originalUnitPrefix (a wikidata item)
JMc: I rearranged the list a bit and suggested simpler naming
We can happily drop "Normalized". I like it better with, but that is simply a matter of taste.
JMc: Is not originalUnitPrefix directly derived from originalUnit?
No, for kilo the original Unit would be gram, original Unit Prefix "k" kilo.
But yes, if we rather want to give each combination of SI prefix and unit a wikidata page, we could do that.
JMc: May be more efficient to store not reconstruct the original value. May even be better to store the original value somewhere else entirely, earlier in the process, eg within the context that you indicate would be worthwhile to capture, because I wouldnt expect alot of retrievals, but you anticipate usage patterns certainly better than I.
Happily. I just try to minimize the number of attributes.
How about just: Datatype: .number (Proposal 4)
:value (xsd:double or xsd:decimal) :unit (a wikidata item) :totalDigits (xsd:smallint) :fractionDigits (xsd:smallint) :original (a wikidata item that is a number object)
Slight correction:
Datatype: measurement (Proposal 5)
:value (xsd:double or xsd:decimal) :unit (a wikidata item) :totalDigits (xsd:smallint) :fractionDigits (xsd:smallint)
Datatype: normalizedMeasurement (inherits measurement)
:original (a wikidata item that is a number object)
Possibly yes. As said above, this implies that all combinations of units and SI prefixes get their own Wikidata item. This is possible to create and could even reflect some of the knowledge about applicable prefixes. Only drawback is that for the normalizedMeasurement fractionDigits is redundant, it will always be totalDigits minus 1, since normalized. But that is a small price for a nicer model.
Gregor