-
The description of `eventID` says
> (The Core Business Vocabulary standard [CBV1.2] specifies the use of a UUID URI for this purpose.)
The examples here use `ni:` URIs that I'm not familiar with.…
-
I'm now reading 2021_03_23b EPCIS 2-0 COMMREV.docx, and I think a subsection **EPCIS Semantics** or **RDF Bindings** is needed to complement the info in sec **10 JSON/JSONLD Bindings**
To cover the…
-
_Originally posted by @mgh128 in https://github.com/gs1/EPCIS/issues/214#issuecomment-807019175_
One particular challenge we have is in formulating JSON-LD in an appropriate way to handle Instance/…
-
ILMD is "Instance/Lot master data" and is defined in EPCIS 1.2 sec 7.3.6 as follows:
(Please, where can I read the draft EPCIS 2.0?)
> descriptive attributes that provide information about one o…
-
Hi,
In the second example, the pre-hash string generated by the package is:
sensorElement
-- sensorMetadata
-- -- deviceID=https://id.gs1.org/8004/4000001111
-- -- deviceMetadata=https://id.g…
-
Hi @mgh128,
We believe that the bizTransaction identifier has been wrongly represented in JSON-LD examples as it does not match any of the URL forms described in _2021_03_29q CBV 2-0 COMMREV_. We c…
-
Examples are great, examples in multiple formats even better.
But if I'm a new developer, how will I know which example demonstrates what?
I think we need an index (README.md) listing all examples…
-
Hi @RalphTro, @mgh128,
According to EPCIS 2.0 draft, the _orderBy_ clause is stated as below:
```
The value of this parameter SHALL be one of: eventTime , recordTime ,
or the fully qualified …
-
The SHACL shape and https://ns.mh1.eu/epcis/ show `xsd:anyURI` as range for several properties. However, `xsd:anyURI` is a **literal** not a URI.
Instead, these props:
- should be defined as `owl:…
-
Hi @mgh128,
Do you think that below example of digital link should be updated as per our current discussion
**As-is**: `"rawData": "https://example.org/giai/401234599999"`
**To-be**: `"rawData":…