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

Alignment with the w3c-ccg traceability vocabulary #122

Closed
PatStLouis opened this issue Feb 6, 2024 · 1 comment
Closed

Alignment with the w3c-ccg traceability vocabulary #122

PatStLouis opened this issue Feb 6, 2024 · 1 comment

Comments

@PatStLouis
Copy link
Contributor

I'm currently assessing the best way to publish credential schemas from this repo on the traceability vocab repository.

There are 2 draft PR's on the traceability vocab repo to draft public schemas around the Mines Act Permit and the Petroleum and Natural Gas Title credentials. These were discussed today during the traceability call. Here are some outcomes:

The traceability group is encouraging BC to submit BC specific credentials and title them as so. Therefore the credential types should figure as so:
BCGovMinesActPermit, BCGovPetroleumAndNaturalGasTitle

The json-ld credentials are usually using CamelCase instead of snake_case to represent keys and values. I will investigate if this would create a technical compatibility issue.

There was one question raised which was to determine if these credentials are a digital representation of physical documents or they are a new numeric data representation. Could someone clarify this? @krobinsonca

I would also like an example of an issued credential with example data, to include into these schemas.

The goal of this step is to engage into discussions from both parties around the interoperability of these credentials.

@PatStLouis
Copy link
Contributor Author

Closing this as we are now aligning with the UNTP specification

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

No branches or pull requests

1 participant