Update Traceability events #70
Conversation
Add association events, fix the model to align better with EPCIS, and add rich documentation.
|
@onthebreeze, I formatted the JSON files. Noting that the context files are full of placeholder values and we need to update with opinionated terms at some point. It's a little unorthodox way of doing it, but I agree on doing this step wise. For example: |
| "disposition": "xsd:string", | ||
| "bizStep": "xsd:string", | ||
| "bizLocation": "xsd:string", | ||
| "sensorElementList": { |
There was a problem hiding this comment.
hey @zachzeus so yeah this is where i was looking, if i have an assertion about a mine location at a date from an independent auditor, is there any way to tie it in here? I want to somehow include whether 3rd party auditors were given access to this mine, i want some way to be able to express that in the traceability vocab if possible
There was a problem hiding this comment.
because what really matters, is if independent 3rd parties had access to observe
Add association events, fix the model to align better with EPCIS, and add rich documentation. closes #39
May go some way to answering #69