[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Why would MS want to make XML break on UNIX, Perl, Python

• To: <xml-dev@l...>
• Subject: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• From: Gavin Thomas Nicol <gtn@r...>
• Date: Thu, 20 Dec 2001 17:42:52 -0500
• In-reply-to: <5C39F806F9939046B4B1AFE652500A3A251A69@R...>
• Organization: Red Bridge Interactive, Inc.
• References: <5C39F806F9939046B4B1AFE652500A3A251A69@R...>

> Or we find an interoperable way to transport/encode the control
> characters (agree on entities or char references or PIs).

I would very much prefer to do this than to allow those naked codes to appear 
in text. I support the idea of finding a way to encode such data, rather than 
include it per se (as per Derek's suggested change in focus).

Numeric character references () are essentially the same as the literal 
data (once parsed the distinction is lost) so I would not support their use.

PI's, while being one mechanism, are application-specific, so are probably 
not ideal.

That leaves us with entities. Perhaps something along the lines of creating a 
"virtual" enitity set in the &Unnnn; space? This was suggested in the ERCS 
days... 

  "an XML 1.1 processor may interpret entity references beginning with the
   letter 'U', followed by 4 hexadecimal characters as representing an
   entity holding the representation of the Unicode Scalar equivalent of 
   the number."

This would provide a standard naming scheme for entities representing code 
points, but leave the exact resolved value undefined. No value is necessary 
anyway, as the entity reference provides all the needed information.

• References:
  • RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
    • From: "Michael Rys" <mrys@m...>

• Prev by Date: Recently published W3C Working Drafts
• Next by Date: Xerces 2.0.0 - DocumentType.getInternalSubset() does it work?!
• Previous by thread: RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• Next by thread: RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• Index(es):
  • Date
  • Thread