questions re the ChainingMetadataProvider type

[Tom Scavo]

I was surprised to find attributes and child elements mentioned on the
ChainingMetadataProvider page [1] but looking at the schema I see that
this is true.

The ChainingMetadataProvider type is based on the abstract
MetadataProviderType and so the former has all the attributes and
child elements of the latter. In the schema, you'll find this
sentence: "Note that metadata filters and the require valid metadata
flag expressed on this configuration overrides those settings on
member providers."

This raises two questions:

1) I understand the comment about the requireValidMetadata attribute
but what about the rest of the Common Attributes? Are they simply
ignored by the parent ChainingMetadataProvider?

2) I don't understand the comment about the metadata filters. Since
filter order matters, the parent ChainingMetadataProvider can't simply
inject a filter into a child provider. The only thing that makes sense
is some kind of override scheme such that if a filter on the parent
ChainingMetadataProvider also exists on a child provider, the former
takes precedence. Likewise if a filter on the parent
ChainingMetadataProvider is not present on *any* child provider, the
filter is ignored. Is that how it works?

Thanks,

Tom

[1] https://wiki.shibboleth.net/confluence/x/NgInAQ