minor changes based on discussions in #79

Author: samuelmr

index.html

@@ -168,7 +168,7 @@ <h3 id="identifiers"><a class="toc-anchor" href="#identifiers" >§</a> Identifie
 <p><strong>Requirement: DIIP-compliant implementations MUST support <a class="term-reference" href="#term:did:jwk">did:jwk</a> and <a class="term-reference" href="#term:did:web">did:web</a> as the identifiers of the <a class="term-reference" href="#term:issuer">Issuer</a>s, <a class="term-reference" href="#term:holder">Holder</a>s, and <a class="term-reference" href="#term:verifier">Verifier</a>s.</strong></p>
 <h3 id="trust-establishment"><a class="toc-anchor" href="#trust-establishment" >§</a> Trust Establishment</h3>
 <p>Signatures in <a class="term-reference" href="#term:digital-credential">Digital Credential</a>s can be used to verify that the content of a credential has not been tampered with. But anyone can sign a credential and put anything in the issuer field. <a class="term-reference" href="#term:digital-credential">Digital Credential</a> ecosystems require that there is a way for a <a class="term-reference" href="#term:verifier">Verifier</a> to check who is the <a class="term-reference" href="#term:issuer">Issuer</a> of a <a class="term-reference" href="#term:digital-credential">Digital Credential</a>. Equally, a user might want to be informed about the trustworthiness of a <a class="term-reference" href="#term:verifier">Verifier</a> before choosing to share credentials.</p>
-<p>DIIP enables trust ecosystems to use <a class="term-reference" href="#term:openid-fed-dcp">OpenID Fed DCP</a> – a light-weight profile of the <a class="term-reference" href="#term:openid-federation">OpenID Federation</a>, authored for use cases including <a class="term-reference" href="#term:wallet">Wallet</a>s and <a class="term-reference" href="#term:digital-credential">Digital Credential</a>s. The <a class="term-reference" href="#term:openid-fed-dcp">OpenID Fed DCP</a> specification is an appendix to this version of the DIIP profile. In the future, the <a class="term-reference" href="#term:openid-fed-dcp">OpenID Fed DCP</a> profile will probably be donated to be maintained elsewhere.</p>
+<p>DIIP enables trust ecosystems to use <a class="term-reference" href="#term:openid-fed-dcp">OpenID Fed DCP</a> – a light-weight profile of the <a class="term-reference" href="#term:openid-federation">OpenID Federation</a>, authored for use cases including <a class="term-reference" href="#term:agent">Agent</a>s, <a class="term-reference" href="#term:wallet">Wallet</a>s and <a class="term-reference" href="#term:digital-credential">Digital Credential</a>s. The <a class="term-reference" href="#term:openid-fed-dcp">OpenID Fed DCP</a> specification is an appendix to this version of the DIIP profile. In the future, the <a class="term-reference" href="#term:openid-fed-dcp">OpenID Fed DCP</a> profile will probably be donated to be maintained elsewhere.</p>
 <p>The requirements regarding Trust Establishment are OPTIONAL in DIIP v5.</p>
 <p><strong>Requirement: DIIP-compliant <a class="term-reference" href="#term:issuer">Issuer</a> <a class="term-reference" href="#term:agent">Agent</a>s MUST support publishing OpenID Federation Entity Configuration as defined in <a class="term-reference" href="#term:openid-fed-dcp">OpenID Fed DCP</a>.</strong></p>
 <p><strong>Requirement: DIIP-compliant <a class="term-reference" href="#term:issuer">Issuer</a> <a class="term-reference" href="#term:agent">Agent</a>s MUST support issuing the <code>fed</code> claim as defined in <a class="term-reference" href="#term:openid-fed-dcp">OpenID Fed DCP</a> when issuing <a class="term-reference" href="#term:sd-jwt-vc">SD-JWT VC</a> credentials.</strong></p>
@@ -360,7 +360,7 @@ <h4 id="entity-identifier"><a class="toc-anchor" href="#entity-identifier" >§</
 <h4 id="issuer-metadata-publication"><a class="toc-anchor" href="#issuer-metadata-publication" >§</a> Issuer Metadata Publication</h4>
 <p><strong>Requirement: The Credential Issuer MUST place the OpenID4VCI issuer metadata into the Entity Configuration, in the <code>openid_credential_issuer</code> property.</strong></p>
 <p><strong>Requirement: The Credential Issuer MUST place the public key material of the keys it uses to sign Digital Credentials in the <code>jwt_vc_issuer</code> property. The <code>jwt_vc_issuer</code> property MUST include the <code>jwks</code> property that contains the Issuer’s JSON Web Key Set as defined in RFC7517.</strong> (The <code>jwt_vc_issuer</code> property MUST NOT include the <code>jwks_uri</code> property.)</p>
-<p><strong>Requirement: If the <code>openid_credential_issuer</code> property is found in the Entity Configuration, the Wallet MUST use only it and ignore the issuer metadata published in the well-known location defined in OID4VCI.</strong></p>
+<p><strong>Requirement: If the <code>openid_credential_issuer</code> property is found in the Entity Configuration, the Wallet MUST use only this medatada and ignore the regular issuer metadata published in the well-known location defined in OID4VCI.</strong></p>
 <p>The Credential Issuer MAY place additional metadata into the <code>federation_entity</code> Entity Type Identifier.</p>
 <p><strong>Requirement: The metadata in the <code>openid_credential_issuer</code> property MUST override the metadata in the <code>federation_entity</code> property.</strong> For example, if both <code>openid_credential_issuer.display.name</code> and <code>federation_entity.organization_name</code> exist, the Wallet MUST show the value of <code>openid_credential_issuer.display.name</code> as the name of the Issuer.</p>
 <h4 id="example-credential-issuer-entity-configuration"><a class="toc-anchor" href="#example-credential-issuer-entity-configuration" >§</a> Example: Credential Issuer Entity Configuration</h4>

spec/federation-profile.md

@@ -50,7 +50,7 @@ The Credential Issuer's Entity Configuration can be found by appending the strin
 
 **Requirement: The Credential Issuer MUST place the public key material of the keys it uses to sign Digital Credentials in the `jwt_vc_issuer` property. The `jwt_vc_issuer` property MUST include the `jwks` property that contains the Issuer's JSON Web Key Set as defined in RFC7517.** (The `jwt_vc_issuer` property MUST NOT include the `jwks_uri` property.)
 
-**Requirement: If the `openid_credential_issuer` property is found in the Entity Configuration, the Wallet MUST use only it and ignore the issuer metadata published in the well-known location defined in OID4VCI.**
+**Requirement: If the `openid_credential_issuer` property is found in the Entity Configuration, the Wallet MUST use only this medatada and ignore the regular issuer metadata published in the well-known location defined in OID4VCI.**
 
 The Credential Issuer MAY place additional metadata into the `federation_entity` Entity Type Identifier.
 

spec/spec.md

@@ -143,7 +143,7 @@ DIIP prefers decentralized identifiers ([[ref: DID]]s) as identifiers. An entity
 
 Signatures in [[ref: Digital Credential]]s can be used to verify that the content of a credential has not been tampered with. But anyone can sign a credential and put anything in the issuer field. [[ref: Digital Credential]] ecosystems require that there is a way for a [[ref: Verifier]] to check who is the [[ref: Issuer]] of a [[ref: Digital Credential]]. Equally, a user might want to be informed about the trustworthiness of a [[ref: Verifier]] before choosing to share credentials.
 
-DIIP enables trust ecosystems to use [[ref: OpenID Fed DCP]] – a light-weight profile of the [[ref: OpenID Federation]], authored for use cases including [[ref: Wallet]]s and [[ref: Digital Credential]]s. The [[ref: OpenID Fed DCP]] specification is an appendix to this version of the DIIP profile. In the future, the [[ref: OpenID Fed DCP]] profile will probably be donated to be maintained elsewhere.
+DIIP enables trust ecosystems to use [[ref: OpenID Fed DCP]] – a light-weight profile of the [[ref: OpenID Federation]], authored for use cases including [[ref: Agent]]s, [[ref: Wallet]]s and [[ref: Digital Credential]]s. The [[ref: OpenID Fed DCP]] specification is an appendix to this version of the DIIP profile. In the future, the [[ref: OpenID Fed DCP]] profile will probably be donated to be maintained elsewhere.
 
 The requirements regarding Trust Establishment are OPTIONAL in DIIP v5.