TODO: Abstract goes here.
TODO: This document represents a concise but limited collection of use cases readers should review alongside the Verifiable Credentials Data Model.
This document is experimental and is undergoing development.
TODO: may not need this
TODO: just point roles in VC use cases
TODO: included this from vc use cases as a template.
Details... Note that our table formatting results are different, but the following can be filled out to yield the desired grouping, and we can tweak the display later if we like.
Since certain credentials may only be issued by accredited institutions, we wish to be able to verify an institution's licence/accreditation to issue.
Focal Use Cases are meant to provide examples where a blend of features from verifiable credentials standard may be used together to solve complex or challenging marketplace needs.
Background of focal use case 1
A verifiable presentation which includes ...along with the assertions that —
TODO: trust hierarchty
There are a number of security considerations that implementers should be aware of when processing data described by this specification. Ignoring or not understanding the implications of this section can result in security vulnerabilities.
While this section attempts to highlight a broad set of security considerations, it is not a complete list. Implementers are urged to seek the advice of security and cryptography professionals when implementing mission critical systems using the technology outlined in this specification.
Write security considerations.
There are a number of accessibility considerations implementers should be aware of when processing data described in this specification. As with any web standards or protocols implementation, ignoring accessibility issues makes this information unusable to a large subset of the population. It is important to follow accessibility guidelines and standards, such as [[WCAG21]], to ensure all people, regardless of ability, can make use of this data. This is especially important when establishing systems utilizing cryptography, which have historically created problems for assistive technologies.
This section details the general accessibility considerations to take into account when utilizing this data model.
Write accessibility considerations.
There are a number of internationalization considerations implementers should be aware of when publishing data described in this specification. As with any web standards or protocols implementation, ignoring internationalization makes it difficult for data to be produced and consumed across a disparate set of languages and societies, which would limit the applicability of the specification and significantly diminish its value as a standard.
This section outlines general internationalization considerations to take into account when utilizing this data model.
Write i18n considerations.