search

gs1 / EPCIS

Draft files being shared for EPCIS 2.0 development
Other
20 stars 7 forks source link

Fixing XSD problem - Unique Particle Attribution, Providing examples for Event Hash IDs and Full combination of fields #323

Closed JaewookByun closed 3 years ago

JaewookByun commented 3 years ago

In applying the latest update of XSD at Jun 23rd, we found a XSD problem called Unique Particle Attribution, because the latest update tried to allow ignoring SBDH for Masterdata capturing. I believe that the community has a consensus of the necessity of the convenience of the optional field; so thus I suggest one way to resolve this issue. The fixed schema is already tested in Oliot EPCIS X prototype.

We would like to share 7 EPCISDocuments in both XML and JSON format that semantically identical and thus should generate identical hash IDs.

We also would like to share the examples for all the event types and master data that have all the (technically) available fields as much as possible. XSD fix, Hash event ID examples, Full combination examples are valid for v2.0 schema and tested in our prototype.

jmcanterafonseca-iota commented 3 years ago

@JaewookByun if you could validate your JSON Documents against #298 that would be great

JaewookByun commented 3 years ago

@JaewookByun if you could validate your JSON Documents against #298 that would be great

@jmcanterafonseca-iota Thank you in the call yesterday. According to your guideline, I generated the latest 'inline' JSON schema draft from #298 . During applying the schema, I found that the schema is almost backward-compatible for our existing examples to comply with the schema. I confirm that the JSON example is validated against the latest schema draft and tested in our prototype, Oliot EPCIS X. Our prototype uses a library, VertX JSON schema validator for validation. The validator abstracts the JSON schema file and check a JSON data whether the data passes the schema or not.

You can access to http://dfpl.sejong.ac.kr/epcis/home/jsonCapture.html load event_with_identical_hash_id_7.json test the validation by clicking isValid button. capture the EPCIS document in the text box by clicking Capture button. or even you can copy, paste, validate, and capture your own EPCIS document. The educational client works with the schema draft at #298 .

To query the stored events or master data, you can use SOAP Query Client and REST Query Client. Unlike the former (The prototyping is done), the latter, Implementing REST service, is now pending in our prototype because there are so many changes and debates in GSMP. There is just one REST endpoint /epcis/resource/events would return XML documents like SOAP Query Client.