Re: [xacml] New issue: proposal for content context path

[Erik Rissanen <erik@axiomatics.com>]

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 <Content> element.  The xpath expression is the value of the RequestContextPath attribute.
>
> I propose the following changes in the core spec (cd-1 PDF):
>
> Replace line 2364 with:
> =============================
> The <AttributeSelector> element returns a bag of values converted from a sequence of nodes selected from a <Content> element in the request context.
> =============================
>
> Delete the full sentence in lines 2366/2367:
> "The <AttributeSelector> element's RequestContextPath XML attribute ...."
>
> Change the definition of RequestContextPath (lines 2422/2423) to:
> =============================
> An XPath expression whose context node is specified by the xpath expression in the value of the ContentContextPath attribute, or the <Content> element of the attribute category indicated by the Category attribute if the ContentContextPath attribute is missing or is a zero-length string....
> =============================
>
> and adding after line 2431:
>
> ============================
> ContentContextPath [Optional]
>
> An XPath expression whose context node is the <Content> element of the attribute category indicated by the Category attribute.  If this xpath expression evaluates to a sequence of more than one node, the evaluation of the AttributeSelector shall return Indeterminate.  The node indicated by this xpath expression SHALL be the context for the xpath expression given by the RequestContextAttribute.
> =============================
>
> Appropriate changes to the schema definition of AttributeSelectorType would also be required.
>
> This change is backward-compatible with existing 3.0 implementations and policies.
>
> Regards,
> --Paul
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>
>