Re: [ws-sx] Issue 88: No XPath default

[Frederick Hirsch <frederick.hirsch@nokia.com>]

Gudge

I am fine with that approach, agree it is better. Goal is to reduce  
ambiguity for interop.

regards, Frederick

Frederick Hirsch
Nokia


On Jul 10, 2006, at 2:49 PM, ext Martin Gudgin wrote:

> I'd rather make the XPathVersion attribute mandatory than have a  
> default
> value.
>
> Gudge
>
>> -----Original Message-----
>> From: Marc Goodner [mailto:mgoodner@microsoft.com]
>> Sent: 10 July 2006 17:06
>> To: Frederick Hirsch; ws-sx@lists.oasis-open.org
>> Subject: [ws-sx] Issue 88: No XPath default
>>
>> Issue 88
>>
>> -----Original Message-----
>> From: Frederick Hirsch [mailto:frederick.hirsch@nokia.com]
>> Sent: Friday, July 07, 2006 10:57 AM
>> To: ws-sx@lists.oasis-open.org
>> Cc: Hirsch Frederick; Marc Goodner
>> Subject: NEW Issue: No XPath default
>>
>> PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL
>> THE ISSUE IS ASSIGNED A NUMBER.
>> The issues coordinators will notify the list when that has occurred.
>>
>> Protocol:  ws-sp
>>
>> ws-securitypolicy-1.2-spec-ed-01-r07-diff
>>
>> <http://www.oasis-open.org/apps/org/workgroup/ws-sx/download.php/
>> 18836/ws-securitypolicy-1.2-spec-ed-01-r07-diff.doc>
>>
>> Artifact:  spec
>>
>> Type: design
>>
>> Title: No XPath default
>>
>> Description:
>> In a number of places an optional attribute is used to indicate the
>> version of XPath to use, with the text "This optional
>> attribute contains
>> a URI which indicates the version of XPath to use."
>>
>> Would it help interoperability to define the default version
>> of XPath to
>> use if attribute is not stated?
>>
>> Places where this occurs:
>> 646 /sp:SignedElements/@XPathVersion
>> 725 /sp:EncryptedElements/@XPathVersion
>> 755 /sp:RequiredElements/@XPathVersion
>>
>> Related issues: none
>>
>> Proposed Resolution: In every instance specify default to use if no
>> attribute specified. Xpath 1.0 (as opposed to 2.0)?
>>
>> regards, Frederick
>>
>> Frederick Hirsch
>> Nokia
>>
>>
>>