lots of EntityAttributes MetadataFilters needed?

[Paul B. Henson]

Looking at the configuration of the EntityAttributesFilter, it seems it is
purely additive? IE, in the example:

<saml:Attribute Name="https://sp.example.org/tagname1">
        <saml:AttributeValue>foo</saml:AttributeValue>
</saml:Attribute>
<Entity>https://sp1.example.org</Entity>
<saml:Attribute Name="https://sp.example.org/tagname2">
    <saml:AttributeValue>foo</saml:AttributeValue>
    <saml:AttributeValue>bar</saml:AttributeValue>
</saml:Attribute>
<Entity>https://sp2.example.org</Entity>

tagname2 = (foo, bar) is added to both sp1 and sp2, while tagname1 is added
to just sp1.

But what if you wanted to add tagname1 = foo to just sp1, and tagname2 =
(foo, bar) to just sp2? Would that require two separate
EntityAttributesFilters?

I was looking at using tags to control attribute release, so there will
be some tags assigned to some sp's, others to others, etc. Unless I'm
misunderstanding, it would basically require one EntityAttributesFilter
per attribute to accomplish?

Thanks...

-- 
Paul B. Henson  |  (909) 979-6361  |  http://www.cpp.edu/~henson/
Operating Systems and Network Analyst  |  henson at cpp.edu
California State Polytechnic University  |  Pomona CA 91768