The reference implementation of the Nuts specification. A decentralized identity network based on the w3c ssi concepts with practical functionality for the healthcare domain.
We have hardcoded validators for NutsAuthorizationCredentials and NutsOrganizationCredentials (and a base validator for any credential). These VC-type-specific validators shouldn't be hardcoded into the Nuts Node: it makes introducing new versions (through releasing a new JSON-LD context version) error-prone and unpractical, because it requires a Nuts Node released.
Validating VC types is a good feature to prevent (hard to debug) mistakes, but the validation rules should be externalized, so they become configuration of the Nuts Node, rather than hardcoded functionality.
Options:
Don't do validation (the lazy solution)
JSON schema (might be weird to combine with JSON-LD)
Make own format (future compatibility issue/lots of work)
We have hardcoded validators for
NutsAuthorizationCredential
s andNutsOrganizationCredential
s (and a base validator for any credential). These VC-type-specific validators shouldn't be hardcoded into the Nuts Node: it makes introducing new versions (through releasing a new JSON-LD context version) error-prone and unpractical, because it requires a Nuts Node released.Validating VC types is a good feature to prevent (hard to debug) mistakes, but the validation rules should be externalized, so they become configuration of the Nuts Node, rather than hardcoded functionality.
Options: