From 551e5deabaf58f38daab9da07b3b29a0dc281075 Mon Sep 17 00:00:00 2001 From: Ian Young Date: Tue, 5 Apr 2011 14:59:20 +0000 Subject: [PATCH] Remove old Shibboleth 1.0 trust schema (two copies) as this is no longer used for anything. --- xml/shibboleth-trust-1.0.xsd | 60 ------------------------------------ 1 file changed, 60 deletions(-) delete mode 100644 xml/shibboleth-trust-1.0.xsd diff --git a/xml/shibboleth-trust-1.0.xsd b/xml/shibboleth-trust-1.0.xsd deleted file mode 100644 index 0e603a5b..00000000 --- a/xml/shibboleth-trust-1.0.xsd +++ /dev/null @@ -1,60 +0,0 @@ - - - - - - - Trust metadata binds keys or authority lists to system entities. - The metadata consumer is responsible for associating the names of system entities - to the application context in an appropriate way. - - - - - - - An optionally signed collection of trust binding elements. - ds:KeyInfo is by definition a binding of a key to a specific entity, - which may be specified in various ways such as KeyName or X509SubjectName. - - - - - - - - - - - - - - - - - - - - - - Binds keying authorities to one or more named system entities. - Omitting ds:KeyName will apply the authorities to all transactions, unless - another specific match applies. This is risky, so use wisely, in conjunction - with constraints on acceptable messages using other forms of metadata or policy. - - - - - - - - - - -