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
{{ message }}
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.
One schema (self referential) for the complete VC or Two schema One for the payload included and a non included schema for the Meta Data of the VC (everything but the payload)
Issues:
If rules block is metadata then does the schema block include it or is it in the meta data schema which requires another schema
If schema no explicit then must be fixed which may be problematic if special cases want to add custom vendor specification fields
if schema not specific to payload than data can't live outside VC which defeats some use cases
Solution:
Nester schema where nested schema blocks have own SAI for that nested block. This allows one to extract the nested schema block for the data payload while still have one schema for the whole VC
Nested Schema:
Main Schema
metadata
rules block
data block
Vendor Specific Metadata
issuerid is the block field name for Vendor actually Issuer specific meta data block
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Discussion 2021-06-07
One schema (self referential) for the complete VC or Two schema One for the payload included and a non included schema for the Meta Data of the VC (everything but the payload)
Issues:
If rules block is metadata then does the schema block include it or is it in the meta data schema which requires another schema
If schema no explicit then must be fixed which may be problematic if special cases want to add custom vendor specification fields
if schema not specific to payload than data can't live outside VC which defeats some use cases
Solution:
Nester schema where nested schema blocks have own SAI for that nested block. This allows one to extract the nested schema block for the data payload while still have one schema for the whole VC
Nested Schema:
Main Schema
metadata
rules block
data block
Vendor Specific Metadata
issuerid is the block field name for Vendor actually Issuer specific meta data block
The text was updated successfully, but these errors were encountered: