-
Dear @CraigRe ,
at the beginning of section 12.1, the draft spec says: "Furthermore, the OpenAPI specifications are available in YAML and JSON at https://www.gs1.org/epcis ."
Two things:
(a) …
-
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…
-
CBV needs to be renamed to Comprehensive:
- §1, pg22, ln197
- §3, pg32, ln391
- §5, pg36, ln434 -
- §6.3, pg44, ln587 -
- §7.3.3.2, pg6…
ghost updated
3 years ago
-
Dear @CraigRe ,
In adjusting the current sensor-related message examples, I just found out that the current version of the CBV does not yet include a sensor measurement type URI for error and alarm c…
-
Hi @CraigRe ,
In the following, you see the introductory sentences on the event dimensions:
line 837: "§ 8 of the CBV defines the data types used in the “What” dimension (...)"
line 908: "This …
-
This update of release number suggests that allowing class-level identification started with 2.0. Appears there was an errata in release 1.2 as well. This should note release 1.1 was the change where …
ghost updated
3 years ago
-
Hi @joelvogt and @mgh128,
Have observed the below example in the draft as well as openapi.yml in top-level resources.
`https://example.com/eventTypes/all/events?EQ_bizStep=urn:epcglobal:cbv:biz…
-
Dear @CraigRe ,
Section 10.2.6 specifies:
"In XML, bizTransactionList contains repeated child elements named bizTransaction, each having an inline type attribute. sourceList and destinationList …
-
Hi @joelvogt and @mgh128 ,
Just a suggestion if it would make sense to clarify in the draft the aggregation logic for CURIE. Possibly it will make the draft comprehensive about the rules involved. …
-
Hi @CraigRe,
In the (IMO very helpful!) table in section 10.2.8, provided by @mgh128, the content in the cells of the very last row is missing (i.e. "Field expects a string from a restricted list …