You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 usingCamelCase
instead ofsnake_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.
The text was updated successfully, but these errors were encountered: