OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xacml] XPath 2.0 support


Oops, the current drafts should have been based on the Errata version, 
which included all the ITU-T changes.

If I can find time, I'll try to do a compare to see what needs to be 
added/changed.  Abbie Barbir and I both did extensive changes which did 
not affect the normative interpretation, but were necessary to meet 
ITU-T requirements.  Since we will want to submit XACML 3.0 for ITU-T 
approval also, the same changes will need to be done.

Regards,
Anne

Erik Rissanen wrote:
> This seems good to me. The OASIS XACML text already has the references, 
> we just need to update them to the final recommendation.
> 
> I made this into issue 81 in the issues list.
> 
> BTW, the current core drafts are based on the OASIS XACML. Is there 
> anything I should bring in from the ITU-T text?
> 
> Regrads,
> Erik
> 
> Anne Anderson - Sun Microsystems wrote:
> 
>> We might also address the related issue of the standard XACML 2.0 
>> datatypes and functions that are defined using references to "XQuery 
>> 1.0 and XPath 2.0 Functions and Operators," W3C Working Draft, 16 
>> August 2002, at 
>> http://www.w3.org/TR/2002/WD-xquery-operators-20020816.  Note this is 
>> a Working Draft, and not a W3C approved Recommendation.  For the ITU-T 
>> standard, since ITU-T does not allow normative references to 
>> non-standards, we inserted into XACML 2.0 itself the text from that 
>> draft necessary to define the affected types and functions, removing 
>> the external dependencies.
>>
>> If we can determine that the definitions in the XPath 2.0 
>> Recommendation are consistent with the definitions used in XACML 2.0, 
>> then we could reference the functions in XPath 2.0 and still preserve 
>> backwards compatibility.  By referencing the XPath 2.0 functions, 
>> XACML implementations could re-use XPath 2.0 function implementations, 
>> or at least feel more free to do so.
>>
>> The affected datatypes are:
>>
>> http://www.w3.org/TR/2002/WD-xquery-operators-20020816#dayTimeDuration
>> http://www.w3.org/TR/2002/WD-xquery-operators-20020816#yearMonthDuration
>>
>> The affected functions, which all have prefix 
>> "urn:oasis:names:tc:xacml:1.0:function:...", are:
>>
>> date-equal
>> time-equal
>> dateTime-equal
>> dayTimeDuration-equal
>> yearMonthDuration-equal
>> anyURI-equal
>> dateTime-add-dayTimeDuration
>> dateTime-add-yearMonthDuration
>> dateTime-subtract-dayTimeDuration
>> dateTime-subtract-yearMonthDuration
>> date-add-yearMonthDuration
>> date-subtract-yearMonthDuration
>> dateTime-greater-than
>> dateTime-greater-than-or-equal
>> dateTime-less-than
>> dateTime-less-than-or-equal
>> date-greater-than
>> date-greater-than-or-equal
>> date-less-than
>> date-less-than-or-equal
>> xpath-node-equal
>> xpath-node-match
>>
>> Regards,
>> Anne
> 
> 

-- 
Anne H. Anderson             Email: Anne.Anderson@Sun.COM
Sun Microsystems Laboratories
1 Network Drive,UBUR02-311     Tel: 781/442-0928
Burlington, MA 01803-0902 USA  Fax: 781/442-1692


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]