Our project currently defines service type values such as maddr and dapregistry in DID Documents. However, all registered DID service types follow a UpperCamelCase (aka PascalCase) naming convention:
LinkedDomains
DIDCommMessaging
CredentialRegistry
OID4VCI
OID4VP
Proposal
This issue proposes changing the service type values introduced for DAPs to use UpperCamelCase. This change will make our DID Documents better aligned with DID conventions and consistent with other implementations.
Proposed changes:
maddr -> MoneyAddress
dapregistry -> DAPRegistry
Implementation
If adopted, this change will require updates to:
DID Document generation code
Parsing code that handles our custom service types
Documentation and examples
Discussion Points
Are there any other custom service types we should include in the DAP specification?
Please share your thoughts and feedback on this proposal.
Context
Our project currently defines service
typevalues such asmaddranddapregistryin DID Documents. However, all registered DID service types follow a UpperCamelCase (aka PascalCase) naming convention:LinkedDomainsDIDCommMessagingCredentialRegistryOID4VCIOID4VPProposal
This issue proposes changing the service type values introduced for DAPs to use UpperCamelCase. This change will make our DID Documents better aligned with DID conventions and consistent with other implementations.
Proposed changes:
maddr->MoneyAddressdapregistry->DAPRegistryImplementation
If adopted, this change will require updates to:
Discussion Points
Please share your thoughts and feedback on this proposal.