You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CBV table 7.6.3 includes detailed Definition. @mgh128 I'm sure you plan to include it in the gs1 RDF?
Same table has "SI Unit": do you plan to match that to Rec20 and and emit it?
The table needs to be revised in view of @mgh128's sync to QUDT. Note: there are some misspellings in col "SI Unit": "siemen" -> "siemens"
Mark, what RDF form do you plan to use? Something like this?
@prefix quantitykind: <http://qudt.org/vocab/quantitykind/> .
@prefix qudt: <http://qudt.org/schema/qudt/> .
gs1:MeasurementType a rdfs:Class, owl:Class;
rdfs:label "Measurement Type"@en;
rdfs:comment "TODO";
skos:exactMatch qudt:QuantityKind.
gs1:canonicalSIunit a rdf:Property, owl:DatatypeProperty;
rdfs:label "canonical SI unit";
rdfs:comment "Canonical SI unit of the measurement type, expressed as a UNECE/UNCEFACT Recommendation 20 code"@en;
rdfs:domain gs1:MeasurementType;
rdfs:range xsd:string.
gs1:MT-Length a gs1:MeasurementType;
rdfs:label "Length"@en;
rdfs:comment "The linear magnitude of any thing, as measured end to end."@en;
gs1:canonicalSIunit "MTR";
skos:exactMatch quantitykind:Length.
The text was updated successfully, but these errors were encountered:
Yes, the intention is that "type" within epcis:SensorReport can take a value from the proposed gs1:MeasurementType or gs1:SensorAlertType code lists as well as a Web URI for a user-defined / vendor-defined value if none of the standard values are appropriate.
VladimirAlexiev
changed the title
make doc text on MeasurementType more precise; add descriptions to RDF
make CBV spec on MeasurementType more precise; add descriptions to RDF
Jun 17, 2021
special
@vocab
for some JSONLD props #265 (comment) describes some discrepancies between EPCIS and CBV that make me and @shalikasingh wonder whether this allows 1. MeasurementTypes, 2. SensorTypes, and/or also 3. User types (values). @RalphTro @CraigRe Please precise these textsThe CBV table 7.6.3 includes detailed Definition. @mgh128 I'm sure you plan to include it in the gs1 RDF?
Same table has "SI Unit": do you plan to match that to Rec20 and and emit it?
The table needs to be revised in view of @mgh128's sync to QUDT. Note: there are some misspellings in col "SI Unit": "siemen" -> "siemens"
Mark, what RDF form do you plan to use? Something like this?
The text was updated successfully, but these errors were encountered: