Skip to content
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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

F-Node-Karlsruhe
Copy link

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:

  • use eventID in VC data model 2.0
  • add artifical id fields in the event

Choosing

"rdfs:subClassOf": {
                "@id": "gs1:GS1DataCredential"
            }

should be discussed

Signed-off-by: F-Node-Karlsruhe <christian.fries@eecc.de>
"rdfs:Class"
],
"rdfs:subClassOf": {
"@id": "gs1:GS1DataCredential"
Copy link
Author

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": {
Copy link
Author

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"
Copy link
Author

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

@F-Node-Karlsruhe
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant