-
Define in ontology (and check props in context):
- epcis:EPCISDocument:
- #223 adds class epcis:EPCISDocument (definition is TODO)
- #223 adds prop epcis:eventList (definition is TODO)
- …
-
https://ns.mh1.eu/epcis/ defines `BizTransaction` as follows:
> A BusinessTransaction identifies a particular business transaction. An example of a business transaction is a specific purchase order. …
-
https://ns.mh1.eu/epcis/ defines two classes thus:
> `BizLocation`: A Business Location is a uniquely identified and discretely recorded location that is meant to designate the specific place where…
-
EPCIS will use WebVoc terms:
- gs1:certificationInfo (#245)
- any `gs1:` props in master data
So how should the EPCIS context (#244) interoperate with the WebVoc context?
- 0: https://github.co…
-
_Originally posted by @mgh128 in https://github.com/gs1/EPCIS/issues/209#issuecomment-807060716_:
What you can read in section 7.4.1.2 of [EPCIS v1.2](https://www.gs1.org/sites/default/files/docs/e…
-
- rename `example artefacts` to `XML`
- I will add 5+6 examples from:
- Examples from https://developers.evrythng.com/docs/epcis-20-repository
- XML to JSON conversion and more examples: https:…
-
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.…
-
_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/…
-
Continuing #231: `2020_07_03y Transaction Event examples.xml` includes rail events that are not represented as JSONLD:
```xml
http://transaction.examplerail.com/pas…
-
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…