OASIS eXtensible Access Control Markup Language (XACML) TC

AttributeSelector as currently defined in the core specification gives an xpath expression with a fixed context node of the 

Hi Paul,

Your proposal for content context path is pretty close to the Selector we
actually use/need need in our use cases.

To enable the full strength of this approach it might be better to have an
ContentContextPath ELEMENT (as child of the Attribute selector) instead of
having an ContentContextPath ATTRIBUTE. 

This simple change will allow to process the value of ContentContextPath
with XACML functions before. Having it encoded as an XML attribute will
prevent this. Further the encoding as proper XML element will also allow for
an explicit AttributeValue (an XPATH attribute value) definition below the

Paul,

I am updating the issues list. Isn't this a duplicate of issue #16? It 
appears to be the essentially the same proposal, except in details in 
the syntax and so on. So I am not creating a new issue number for this.

Best regards,
Erik

Paul Tyson wrote:
> AttributeSelector as currently defined in the core specification gives an xpath expression with a fixed context node of the