After reviewing this issue I see no way to get the functionality I wanted without introducing bags or bags or a solution of equal complexity. I now agree with Erik that the benefits of this are not worth the additional complexity.
I suppose that if someone really needed to deal with multiple intermediaries, codebases or receivers, they could create additional subject category identifiers, e.g. intermediary1, intermediary2, ...
I now agree we should close both issues without action. Erik, thank you for the time you have put into it.
Hal
>
Original Message-----
> From: Erik Rissanen [mailto:erik@axiomatics.com]
> Sent: Thursday, June 19, 2008 3:14 PM
> To: xacml
> Subject: [xacml] Issues #71 and #76 (multi-categories)
>
> All,
>
> During the call today Hal expressed an interest in pursuing issues #71
> and #76.
>
> To keep up the momentum I am posting my thoughts on these issues.
>
> To remind everybody, these issues are the issues about extending XACML
> to support multiple distinct categories of attributes, for example:
>
>
>
> Note that both of the Attributes elements contain the same category. In
> XACML 2.0 a similar construct, that is, multiple