>I can do all this through custom datatypes and attributes - I
understand - as I said I was more curious to understand the rationale
than anything else...
I think rationale for sticking it to the Resource is historical - XACML
started as a way to protect XML document, IIRC the initial TC docs.
Rationale for leaving only one content is to have only one root for the
selector and not having to add separate selectors or switches.
And as, logically, single content is sufficient for the whole context
representation, this slightly non-intuitive naming and placement
persists.
Daniel;
