Metadata driven configuration: name format and xsd schema

[Wessel, Keith]

That all makes sense, but that might be a useful note to include on the MetadataDrivenConfiguration page, then. After all, as I stated in my last note, it'd be nice if the examples on the wiki worked with the configuration files out of the box. I don't expect (or want) every namespace defined, but with no mention on that page and nothing in the distributed config, how am I supposed to know what namespace xsd is supposed to be mapped to? Am I missing something?

Keith


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Friday, September 25, 2020 11:12 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Metadata driven configuration: name format and xsd schema

On 9/25/20, 12:06 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

> I'm not sure why I'm not seeing the xsd namespace in the shipped version of the metadata-providers.xml.

We don't just define every possible namespace and even if we tried, as soon as something new got used, every existing file would be "wrong" if you were applying that standard.

The XML is solely the deployer's responsibility. You're adding a namespace there so you have to declare it if it's not declared.

Adding them by default is a convenience, not an assumption.

-- Scott


-- 
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net