Open VladimirAlexiev opened 2 years ago
Public review draft CBV §7.8.3 shows these enumerations for component
lower case as above.
Sensor data examples 10, 14, 15 also use lower-case values.
Regarding geocoordinate
I think I agree that this could/should be removed because it's not being used to distinguish one component from another in the way that x
, y
, z
or northing
vs easting
do. I'll therefore submit a review comment asking the group to consider removing geocoordinate
from this table.
I'll submit a separate review comment asking the group to consider whether the enumerated values for component
should be lower-case, all-caps or only with capitalisation of the initial letter, the latter being consistent with the approach for values of type
(e.g. gs1:AbsoluteHumidity , gs1:Temperature ) currently under GMD SMG review.
@mgh128 Good!
I pulled and checked, currently ALL jsonld examples use lowercase component
:
cd ../JSON-simple-context/
grep component *.jsonld */*.jsonld
So I vote to keep it lowercase.
However:
WithSensorData/SensorDataExample10.ttl: epcis:component cbv:COMP-Z
epcis:component <example:x>
(#356)WithSensorData/SensorDataExample10.ttl: epcis:component "X"
Checked again:
@dakbhavesh or @RalphTro can you fix this last bullet? Eg https://github.com/gs1/EPCIS/blame/master/JSON-simple-context/WithFullCombinationOfFields/aggregation_event_all_possible_fields.jsonld#L98
Dear @VladimirAlexiev , Gladly. Done!
Hmm, the last change I see in https://github.com/gs1/EPCIS/tree/master/JSON-simple-context/WithFullCombinationOfFields is on Apr 19, 2022
component
field in newest context has this enumeration:@mgh128
geo:
URL). What we discussed, and what SensorDataExample16.jsonld shows, and what WithSensorData/README.md describes is a simpler way:Why do you want the more complex way with
geocoordinate
? And what would be "type" in that case?If you agree, please remove
geocoordinate
from context and from CBV.ttl.If you disagree, let's vote and then add a bit more from README into rdfs:comment (use new lines with '"""') and into rdfs:seeAlso. Citing README:
SensorDataExample16.jsonld
: Event conveying the same coordinates using the geo: URI scheme (RFC5870), which is a much shorter way.geo:
URIs can use only two fixed CRS (see RFC5870 section 8.3 and IANA geo-uri-parameters:EPSG::4326
, which is WGS84 (2D)EPSG::4979
, which is WGS84 with altitude (3D)component
andcoordinateReferenceSystem
can use any EPSG or OGC coordinate system