xacml — archive

[System]

>In ver 0.8 function draft, string comparison (set against a value) is >differently specified in MatchId from Apply. Suppose attribute selector >returns a sequence (e.g. "aaa" and "bbb"). In ResourceMatch, >function:string-equal is used while in Apply, function:string-member-of >is used: No - it was not.. You could use member-of in match just as easily - at least in the last draft I had anything to do with. As well as set-equal. All your use cases WERE already covered. <ResourceMatch MatchId="function:member-of"> <AttributeSelector RequestContextPath="/a/b/c/text()"> <AttributeValue>bbb</AttributeValue> </ResourceMatch> >We fix the above problem by using the higher-order bag function >specified in 0.9 function draft: How is that a fix? That you can now use "string-greater" for target matching and all implementations have to support it? We are trying to fix a NON existing problem. Daniel;