W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2006

[Bug 2441] xqx: character references

From: <bugzilla@wiggum.w3.org>
Date: Fri, 29 Sep 2006 00:41:05 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1GT6R7-00007v-Ah@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2441





------- Comment #16 from maxim.orgiyan@oracle.com  2006-09-29 00:41 -------
> > "Each predefined entity reference is replaced by the character it represents
> > when the string literal is processed."
> 
> There are five predefined entities, including amp and that means that &amp;
> gets replaced by an ampersand character. The whole point of writing &amp;
> rather than & is to _stop_ it being used as markup so it is absolutely clear
> that in XQuery as in XML 
> &amp;#1234;is the 7 characters 7 # 1 2 3 4 ; not a reference to the character
> with codepoint 1234. It would be absolutely bizare if Xquery were defined
> otherwise, as it would be using XML syntax with completely different semantics.
> 
> > Are string-length("abc&#x1D156;def") and string-length("abc&amp;#x1D156;def")?
> > at least one XQuery processor I tried resolves these two strings to the same
> > string value,
> bugs happen, report it as a bug to that system's maintainers, That is
> unquestionably a bug.

>>> Ok. Well, I would interpret this in the
>>> same way. My point, however, is that
>>> this is not stated anywhere in the XQuery spec - that 
>>> what I mean by "ambiguity".
>>>
>>> I am validating w/ Jim whether this is the intended meaning.
Received on Friday, 29 September 2006 00:41:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:15 UTC