20-Jan-26

Author: selfissued

openid-federation-1_0.xml

@@ -78,7 +78,7 @@
       </address>
     </author>
 
-    <date day="19" month="January" year="2026"/>
+    <date day="20" month="January" year="2026"/>
 
     <workgroup>OpenID Connect Working Group</workgroup>
 
@@ -1676,7 +1676,7 @@
         <t>
           The <spanx style="verb">issuer</spanx> parameter value
           in the <spanx style="verb">openid_provider</spanx> metadata MUST
-          match the Federation Entity identifier
+          match the Federation Entity Identifier
           (the <spanx style="verb">iss</spanx> parameter within the Entity Configuration).
         </t>
 
@@ -1805,7 +1805,7 @@
         <t>
           The <spanx style="verb">issuer</spanx> parameter value
           in the <spanx style="verb">oauth_authorization_server</spanx> metadata MUST
-          match the Federation Entity identifier
+          match the Federation Entity Identifier
           (the <spanx style="verb">iss</spanx> Claim in the Entity Configuration).
         </t>
 
@@ -4613,7 +4613,7 @@ Content-Type: application/json
                 <vspace/>
                 REQUIRED. The Trust Anchor that the resolve endpoint
                 MUST use when resolving the metadata.
-		The value is an Entity identifier.
+		The value is an Entity Identifier.
 		<vspace blankLine="1"/>
 		The <spanx style="verb">trust_anchor</spanx> request parameter
 		MAY occur multiple times, in which case,
@@ -10405,7 +10405,7 @@ HTTP/1.1 302 Found
 	    </address>
 	  </author>
 
-          <date day="19" month="January" year="2026"/>
+          <date day="20" month="January" year="2026"/>
         </front>
       </reference>
 
@@ -10461,7 +10461,7 @@ HTTP/1.1 302 Found
 	    </address>
 	  </author>
 
-          <date day="19" month="January" year="2026"/>
+          <date day="20" month="January" year="2026"/>
         </front>
       </reference>
 
@@ -13283,7 +13283,7 @@ Host: op.umu.se
             <spanx style="verb">openid_provider</spanx>.
           </t>
           <t>
-            Entity identifier paths are now included when using the Federation API,
+            Entity Identifier paths are now included when using the Federation API,
             enabling use in multi-tenant deployments sharing a common domain name.
           </t>
           <t>