All,
Issue 71 proposes that multiple Attributes elements with the same
category should be treated as distinct elements.
This is contrary to how it was in 2.0 and how 3.0 is currently.
I propose that we do not adopt the proposal and that issue 71 is closed
without action.
There are two reasons for this:
1) A minor reason is that it clashes with the multiple request syntax.
But this would be trivial to fix by introducing some other syntax for
the multiple requests.
2) It significantly changes the behavior of the very basics of XACML.
The current AttributeDesignator functionality breaks since then it is no
longer clear which particular instance of an