attribute filter rule : permit ANY by default ?
Cantor, Scott
cantor.2 at osu.edu
Tue Aug 6 19:44:05 EDT 2013
On 8/6/13 5:07 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>Looking at the couple of attribute-filter.xml files that folks sent
>me, it looks like the most common stanza is :
>
><AttributeRule attributeID="foo">
> <PermitValueRule xsi:type="basic:ANY" />
></AttributeRule>
>
>which makes me think that a default permit any value rule would
>shorten configurations, so instead :
>
> <AttributeRule attributeID="foo" />
Or perhaps an XML attribute if we wanted to be pedantic:
<AttributeRule attributeID="foo" permitAny="true"/>
But I don't think defaulting it is a bad thing, no. I'm known for
"implicit" configuration design though, and have been knocked for it. I
think it works fine for people familiar with the system, and not so much
for learning. I don't think we have to heavily advertise that approach,
but for experts, sure.
-- Scott
More information about the dev
mailing list