W3C home > Mailing lists > Public > xsl-editors@w3.org > July to September 2005

Comments on XSL 1.1 from Felix Sasaki (team contact of I18N Core WG)

From: Felix Sasaki <fsasaki@w3.org>
Date: Sat, 17 Sep 2005 00:23:31 +0900
To: xsl-editors@w3.org
Cc: "member-i18n-core@w3.org" <member-i18n-core@w3.org>
Message-ID: <op.sw7bphemx1753t@ibm-60d333fc0ec>

Dear XSL Working Group,

With this mail I'm sending you comments about xsl 1.1, which I produced as  
part of my work in the i18n core wg. I created these comments on my own  
and distributed them in our group, but the i18n core wg did not have time  
to discuss them on a telefon conference. So please regard these comments  
as my private comments, without explicit disagreement from the other  
working group members.
I hope that these comments will be helpful for the further development of  
your document, which is already an excellent piece of work. And I'm  
looking forward to your feedback

Best regards,

Felix Sasaki (team contact of the i18n core wg)

P.S.: Currently the comments are just in this mail, but later I will  
integrate them into the review history page of the i18n core wg, cf.
http://www.w3.org/International/reviews/

-------------------------------------------

URI of the spec: http://www.w3.org/TR/2005/WD-xsl11-20050728/

[1] http://www.w3.org/TR/2005/WD-xsl11-20050728/#xml:lang
"A language and/or country specifier in conformance with [RFC3066]":
Please refer also to the successor of RFC 3066, i.e. please write "A
language and/or country specifier in conformance with [RFC3066] or its
successor".

[2] sec. 2.2: Do you support names in the sense of xml 1.1, i.e.
http://www.w3.org/TR/2004/REC-xml11-20040204/#NT-Name ?

[3] General: Have you thought about formatting of ruby, cf.
http://www.w3.org/TR/ruby/ ?

[4] editorial: It would be good to have links to the various sections in
the indirectly-derived traits overview (end of sec. 4.1)

[5] editorial: the links to targets in this list (e.g.
http://www.w3.org/TR/2005/WD-xsl11-20050728/#linebuilding-6) don't work.

[6] editorial: longdescriptions are encoded in iso-8859-1, e.g.
longdesc/InlineExampleMixed.2a.html , whereas the main document is encoded
in utf-8.

[7] 5.4.6 The Language Property: Please refer to RFC3066 or its successor
for the construction of language codes.

[8] editorial: ISO639-3 is in the reference section, but not in the main
text.

[9] editorial: linebreak of code in examples does not work sometimes, see
e.g. the example "This example shows a very simple page layout
specification. ".

[10] 5.11 Property Datatypes, the datatypes for name and character: please
refer to the productions of xml 1.1 instead of xml 1.0.

[11] 5.11 the datatypes country, language and script: The revision of RFC
3066,
http://www.ietf.org/internet-drafts/draft-ietf-ltru-registry-12.txt
solves some problems which arise with the the underlying ISO standards
(e.g. reliability of values, matching of values). You might have a look
into this.

[12] 5.11 uri-specification: please refer to rfc 3987 (IRI) instead of
2396, and add a normative reference to rfc 3987.

[13] In 7.10.1 "country": you refer to RFC3066; in other sections, you
refer to the ISO country codes. Please be more coherent. We would propose
a solution like in the comment [11].

[14] 7.10 "hypenation properties": these properties are also sensitive to
RFC3066, so please think about a solution like [11].

[15] Reference to Unicode: Please change the reference to the Unicode
standard as described in
http://www.w3.org/TR/charmod/#sec-RefUnicode , e.g.

Unicode
The Unicode Consortium, The Unicode Standard, Version 4.1.0, ISBN
0-321-18578-1, as updated from time to time by the publication of new
versions. (See http://www.unicode.org/unicode/standard/versions for the
latest version and additional information on versions of the standard and
of the Unicode Character Database).

[16] 7.26: why don't you refer to the definitions of xslt 2.0 for number
to string conversions?

[17] 7.26 and in other parts of the spec: "In the XML markup of the figure
above, the characters are represented by their presentation form (and not
their Unicode code points). The order in which the characters are depicted
is their storage order. " You might introduce the terminology "logical
order" (which you named storage order) and "visual display", see also
http://www.w3.org/TR/charmod/#sec-LogicalOrder

[18] 7.29.7: "This version of the writing-mode property covers the base
writing-modes that are used as the official languages of the United
Nations." Should this be "This version of the writing-mode property covers
the base writing-modes that are used *for* the official languages of the
United Nations."?

[19] 7.30 xml:lang: For this comment, see also comment [11].
Received on Friday, 16 September 2005 15:23:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:58 GMT