W3C home > Mailing lists > Public > public-xmlsec@w3.org > March 2011

Re: Does Dsig 2.0 allow URIs with fragment identifiers

From: <Frederick.Hirsch@nokia.com>
Date: Tue, 1 Mar 2011 15:02:07 +0000
To: <pratik.datta@oracle.com>
CC: <Frederick.Hirsch@nokia.com>, <public-xmlsec@w3.org>
Message-ID: <74F0AD55-5448-438C-B84C-67E6D23723D1@nokia.com>
I think we should support this type of URI for usability and simplicity.

This is consistent with your proposed change, isn't it?

  I need to modify it to say something like this -  The IncludedXPath cannot be present if the URI has a fragment identifier.

regards, Frederick

Frederick Hirsch
Nokia



On Mar 1, 2011, at 3:01 AM, ext Pratik Datta wrote:

Should we allow   <dsig2:Selection> to have a URI of the form

http://example.com/bar.xml#chapter1

i.e containing a fragment identifier at the end e.g.  "#chapter1"

this means that the implementation need to remove the fragment identifier from the URI, resolve the modified URI, parse it into XML and then look for an element containing an id of specified in the fragment.  I am not sure if this was MANDATORY to implement in Dsig 1.0.


There is currently an inconsistency in section 10.6.1
In the first para it says that URI attribute is required, but later on it says that either URI attribute should be present or IncludedXPath should be present.  I need to modify it to say something like this -  The IncludedXPath cannot be present if the URI has a fragment identifier.

Pratik
Received on Tuesday, 1 March 2011 15:02:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 March 2011 15:02:53 GMT