W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > April to June 2000

Re: XPath Serialization

From: Martin J. Duerst <duerst@w3.org>
Date: Fri, 26 May 2000 15:43:56 +0900
Message-Id: <4.2.0.58.J.20000526154147.0358d220@sh.w3.mag.keio.ac.jp>
To: "John Boyer" <jboyer@PureEdge.com>, "IETF/W3C XML-DSig WG" <w3c-ietf-xmldsig@w3.org>
At 00/05/23 11:04 -0700, John Boyer wrote:
>Hello all,
>
>Attached is the latest version of the XPath serialization spec.  The
>following changes were made:
>
>1) Changed character reference rendering to be uppercase hexadecimal with no
>leading zeroes (e.g. &#xD; instead of &#x0D;).  This was decided at the
>Victoria FTF.
>
>2) Added the function here() to the XPath function library based on requests
>by the group at and after the Victoria FTF.  You want to have a look at it,
>though, because it is defined slightly differently than in the current
>XPointer draft.  Basically, they define it to return the element containing
>the attribute or text node that bears the Xpath expression.  I changed that
>to returning the actuall attribute, text or other node (if you want the
>element, you can get the parent, but if you are given an element, but it has
>more than one attribute bearing an Xpath, then there is room for ambiguity.
>
>I need feedback on this function, esp. from other implementers.

I'm not an implementer, but it is very clear that defining a function
with the same name but different behaviour is a very bad idea.
Either (preferred) just do what XPointer does, or rename your
function.


Regards,   Martin.
Received on Friday, 26 May 2000 02:38:28 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:09 GMT