OASIS eXtensible Access Control Markup Language (XACML) TC

While working out what the spec says about requests for decisions on XML
resources, I found some features that appear to be underspecified.

Line numbers refer to cd-1 PDF core spec.

Item #1. XPathCategory xml attribute

This appears in the examples in the core spec, and is mentioned on line
3890.  However, it does not appear in the element description for

>> The core spec should provide better definition of the semantics and
>> processing expectations for resource:xpath.

I agree. I asked about this on the mailing list about a month ago and got
no response.

Regards,
Craig

---
craig forster | staff software engineer | ibm australia development labs
http://blogs.tap.ibm.com/weblogs/craigforster/


                                                                                                                                                      
  From:       "Tyson, Paul H" 

Paul,

See responses inline:

Tyson, Paul H wrote:
> While working out what the spec says about requests for decisions on XML
> resources, I found some features that appear to be underspecified.
>
> Line numbers refer to cd-1 PDF core spec.
>
> Item #1. XPathCategory xml attribute
>
> This appears in the examples in the core spec, and is mentioned on line
> 3890.  However, it does not appear in the element description for
> 

Erik Rissanen wrote:
>> Item #2. urn:oasis:names:tc:xacml:1.0:resource:xpath
>>
>> This appears in the examples, but not in the conformance table (10.2.6).
>> The brief explanation on line 5120 does not specify any datatype, nor
>> does it clarify how resource:xpath differs from resource:resource-id
>> when used for XML resources.  It does not explain the difference
>> between:
>>
>>     (a)
>> Attribute[@AttributeId='resource-id'][@DataType='xpathExpression']
>>     (b) Attribute[@AttributeId='xpath']
>>
>> The example in 4.2.2 includes both these