-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add epcis context and ontology #10
base: main
Are you sure you want to change the base?
add epcis context and ontology #10
Conversation
Signed-off-by: F-Node-Karlsruhe <christian.fries@eecc.de>
"rdfs:Class" | ||
], | ||
"rdfs:subClassOf": { | ||
"@id": "gs1:GS1DataCredential" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question:
Is GS1DataCredential the right choice here?
"EPCISDocumentCredential": { | ||
"@id": "gs1:EPCISDocumentCredential" | ||
}, | ||
"EPCISEventCredential": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we leave EPCISEventCredential out in VC-Data-Model 1.x?
"EPCISEventCredential": { | ||
"@id": "gs1:EPCISEventCredential" | ||
}, | ||
"@import": "https://ref.gs1.org/standards/epcis/2.0.0/epcis-context.jsonld" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not necessary if the EPCIS Document/Event carries its own context, as it's supposed to
Added EPCISDocumentCredential and EPCISEventCredential types
The second is questionable in VC Data Model 1.x as EPCIS events do not have an id field which could be used as subject.id
Options:
Choosing
should be discussed