From e81b3d3ef62b174ca81a208f2046fb588bd7fc37 Mon Sep 17 00:00:00 2001 From: Giuseppe De Marco Date: Thu, 19 Sep 2024 12:52:03 +0200 Subject: [PATCH] fix: clarification about metadata in subordiante statements --- openid-federation-wallet-1_0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openid-federation-wallet-1_0.md b/openid-federation-wallet-1_0.md index 8640788..0b41834 100644 --- a/openid-federation-wallet-1_0.md +++ b/openid-federation-wallet-1_0.md @@ -421,7 +421,7 @@ These modifications allow a federation authority, such as a Trust Anchor, to app The key difference between `metadata` and `metadata_policy` is that metadata directly affects only the Immediate Subordinate Entity, while `metadata_policy` impacts the configuration of all Subordinate Entities along a Trust Chain, as defined in Sections 5 and 6.1 of [@!OpenID.Federation]. -This distinction positions the `metadata` parameter as an ideal tool for federation authorities managing entity registrations and needing to sanitize Leaves configurations in an arbitrary way. The Trust Anchor (TA) and Intermediate (INT) sanitize an Entity Configuration during technical tests and finalize it by setting specific metadata parameters. +This distinction positions the `metadata` parameter as an ideal tool for federation authorities managing Immediate Subordinates registrations and needing to sanitize Leaves configurations in an arbitrary way. The Trust Anchor (TA) and Intermediate (INT) sanitize an Entity Configuration during technical tests and finalize it by setting specific metadata parameters. ## Using Metadata Policies