W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2004

[XPointer] I18N last call comments

From: Martin Duerst <duerst@w3.org>
Date: Sun, 15 Feb 2004 16:39:39 -0500
Message-Id: <>
To: public-qt-comments@w3.org
Cc: w3c-i18n-ig@w3.org

Dear XML Query WG and XSL WG,

Below please find the I18N WGs comments on your last call document
"XML Path Language (XPath) 2.0"

Please note the following:
- These comments have not yet been approved by the I18N WG. Please
   treat them as personal comments (unless and) until they are approved
   by the I18N WG.
- Please address all replies to there comments to the I18N IG mailing
   list (w3c-i18n-ig@w3.org), not just to me.
- The comments are numbered in square brackets [nn].
- Because XQuery in big parts is identical to XPath, many of these
   comments also apply to XQuery. We are confident that you can
   figure this out yourselves.

[1] URIs: Throughout this and other specs, URIs have to be changed
   to IRIs.

[2] Current date and time: It should be made explicit that this has to
     include a timezone.

[3] Implicit time zone: This has to be removed. Using implicit conversions
     between timezoned and non-timezoned dates and times is way too prone
     to all kinds of subtle and not so subtle bugs.

[4] operation tree normalization: There are many different
     normalizations in this series of specifications. These should be
     clearly and carefully separated.

[5] 3.1.1: The Note says that the characters used to delimit the literal
     must be different from the characters that are used to delimit the
     attribute. This is not strictly true, &quot; or so can also be used.

[6] 3.1.5: conversion rules: to what extent can strings, elements
     with string content, and elements allowing mixed content but
     actually only containing a string be mixed? This is important
     for some I18N applications.

[7] How to test for an element that only contains text
     (independent of type)? This is important for some I18N applications.

[8] 3.5.1: What about elements that have more elaborate types (e.g. mixed),
     but that still don't contain anything more than a string?
     This is important for some I18N applications.

[9] 3.10.2: How to cast between complex types?

[10] References: The reference to ISO/IEC 10646 should be updated to
      the newest version.

Regards,    Martin.
Received on Sunday, 15 February 2004 16:40:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:17 UTC