W3C home > Mailing lists > Public > www-i18n-comments@w3.org > September 2002

Character Model Comments Clarifications

From: Mark Scardina <mark.scardina@oracle.com>
Date: Tue, 10 Sep 2002 14:18:28 -0700
To: "'Martin Duerst'" <duerst@w3.org>, <www-i18n-comments@w3.org>
Cc: "'W3c-Xsl-Wg@W3. Org'" <w3c-xsl-wg@w3.org>
Message-ID: <000801c2590f$9baccd90$4d0e2382@us.oracle.com>

Martin regards the issues below our responses are inline.

1) http://lists.w3.org/Archives/Member/w3c-xsl-wg/2002Aug/0044.html

[XSL] To clarify, our concern was based on first not seeing a clear
definition of a private system and second, based upon what we inferred a
private system to be, why should it fall under the prevue of your spec.
It obviously could not be enforced.

2) http://lists.w3.org/Archives/Member/w3c-xsl-wg/2002Aug/0045.html

[XSL] XSLT allows and needs manipulation of character sequences at any
boundaries not simply entity boundaries.  An XSLT stylesheet itself can
expose non-normalized strings in an effort to match sequences in a 1.0
document.  It is also not just about serialized XML as processes can
exchange result trees which would mean working with the DOM which is not
addressed in your spec.

3) http://lists.w3.org/Archives/Member/w3c-xsl-wg/2002Jul/0088.html
For 3), we asked for clarification on one part of your comment.
Actually, we would like you to clarify both sentences. There was some
follow-up discussion on 3), but this didn't really clarify the comment
itself. If you think that you need to make another comment, please check
the comments you have already made, and if you think there is something
missing, please submit another comment asap.   

[XSL] Regarding our first sentence, Section 3.5 covers a number of
processing scenarios and conditionals in one long paragraph making it
difficult to parse and properly evaluate.  Our suggestion was to break
this up structurally with additional context so that the types of
processes and their exceptions were better delineated.

[XSL] Regarding the second sentence, Anders already responded with some
examples, but the essence is that XSL and XML for that matter must be
able to represent non-Unicode characters inside attributes as well as

Mark V. Scardina              Group Product Mgr & XML Evangelist 
CORE & XML DEVELOPMENT GROUP  E-mail: Mark.Scardina@oracle.com 
Web Site: http://otn.oracle.com/tech/xml/ 
Received on Tuesday, 10 September 2002 17:18:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:14 UTC