Closed paulengland closed 3 months ago
See also #26.
Per discussion in meeting, having a map leaves room for us to add additional (optional) fields in later versions of this specification.
Perhaps one of the additional fields is a human-readable statement of intent behind the edits.
PR #75 introduced a to-be-signed data structure; after that, I think #26 describes the need for the credential subject's role to be documented. Closing as redundant.
Claims have a couple of text fields that can be used to provide info about the claim generator. Do we need something similar for ID assertions? For example, if a manifest contains three ID assertions by three different key-holders, should we provide a field to (e.g.,) encode what role these signers are playing? (fact checker, editor, journalist...)