[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ws-sx] Potential XPath Issues for WS-SecurityPolicy
Paul Yes, you are correct. > (2) define a limited set of XPath expressions that MUST be supported > by an implementation (and list explicitly ) is new. regards, Frederick Frederick Hirsch Nokia On Jan 18, 2006, at 9:25 PM, ext Paul Cotton wrote: > Am I correct in assuming that item (1) below was discussed on today's > WS-SX call but item (2) is new? > > /paulc > > Paul Cotton, Microsoft Canada > 17 Eleanor Drive, Nepean, Ontario K2E 6A3 > Tel: (613) 225-5445 Fax: (425) 936-7329 > mailto:Paul.Cotton@microsoft.com > > > > > >> -----Original Message----- >> From: Frederick Hirsch [mailto:frederick.hirsch@nokia.com] >> Sent: January 18, 2006 10:22 AM >> To: ws-sx@lists.oasis-open.org >> Cc: Hirsch Frederick >> Subject: [ws-sx] Potential XPath Issues for WS-SecurityPolicy >> >> Some potential issues related to XPath in WS-SecurityPolicy. >> >> (1) In the SignedElements and EncryptedElements policy assertions of >> WS-SecurityPolicy, an XPath expression is used to specify what >> elements should be signed/encrypted. However, there appears to be no >> text that says an XPath MUST be namespace-qualified (and examples >> have not ns-qualified the XPaths). >> >> Proposed resolution: add text saying that an XPath expression MUST be >> namespace qualified >> >> (2) define a limited set of XPath expressions that MUST be supported >> by an implementation (and list explicitly ) >> >> regards, Frederick >> >> Frederick Hirsch >> Nokia >> >> >> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]