Implementation Guide April 24 #568
Conversation
| In addition, issuers may issue these types and make use of issuer identifier | ||
| types (DID methods), cryptographic key or signature types, status methods, or | ||
| other Verifiable Credentials options beyond those known to the OB/CLR spec. | ||
| These additional components may be noted as possibilities in future updates to |
There was a problem hiding this comment.
These additional components may be noted as possibilities in future updates to
the OB/CLR specs, but for best interoperability within OB/CLR tools and
conformance certification from 1EdTech, support for a issuer identifier, key
type, signature type, and (if applicable) status method mentioned in these
specifications.
The latter part of this sentence is incomplete/doesn't make sense or finish the thought.
There was a problem hiding this comment.
Changed to:
These additional components may be noted as possibilities in future updates to
the OB/CLR specs, but for best interoperability within OB/CLR tools and
conformance certification from 1EdTech, issuers should support issuer
identifiers, key types, signature types, and (if applicable) status methods
mentioned in these specifications.
Does it make more sense now, @justinpitcher ?
April release for Implementation Guide: