-
Currently, ../events and ../events/{eventID} endpoint return EPCISDocument. EPCIS 1.2 usesEPCISQueryDocument for responses. I'll update events endpoints accordingly
-
Are there any examples of how to format extensions in JSON? Specifically for custom ILMD or custom event-level data. It is unclear how to incorporate custom data into our EPCIS output that isn’t defin…
aopel updated
3 years ago
-
Dear @CraigRe ,
A minor editorial thing: As is, the following sentence is part of the eventID field definition: "(The Core Business Vocabulary standard [CBV1.2] specifies the use of a UUID URI for…
-
Hi @mgh128, While going through latest draft it struck me that we need to update the SHACL definition file to accommodate single event EPCIS JSON body structure.
-
Hi @joelvogt, @mgh128,
1. Line: 3834 **as-is:** "The EPCIS REST bindings provide an interface based on Representational State Transfer (REST) architecture style [REST]" **to be:** "The EPCIS REST …
-
Hi @joelvogt, @mgh128,
Including a few EPCIS Documents in JSON format depicting error declaration and error correction events will be helpful.
-
A friendly suggestion...
For the following classes:
- PostalAddress
- Place
- GeoCoordinates
and attributes within those classes, please consider referencing schema.org URIs for those where…
-
Hi @CraigRe ,
A couple of further minor things I came across:
- Section 10.1.1: "Declarations within XML Schema Definition language (XSD) link a named element to a define data structure." ==> defin…
-
JSON/JSON-LD is not mentioned as something else that would appear in Monospace. Should it and should Monspace be used for the JSON/JSON-LD specific text in chapter 10?
§4, pg33, ln401
ghost updated
3 years ago
-
Is this line intending to focus on EPC? Or is the intent to suggest EPCIS/CBV more broadly?
§2.4, pg30, ln342
ghost updated
3 years ago