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

Possible changes for XML 2nd Edition

  • From: John Cowan <jcowan@r...>
  • To: "xml-dev@x..." <xml-dev@x...>
  • Date: Wed, 24 May 2000 14:51:43 -0400

professional xml 2nd edition
The XML Core WG would like input from the xml-dev public, particularly
those of you who have implemented XML parsers, on the following points:

Issue PE28:

Currently the XML Recommendation is silent about the handling of
documents that contain "impossible" bytes.  For example, the byte 0xFF
cannot appear in any UTF-8 encoded document.  We are considering making
such violations of the encoding a fatal error.

PRO: an improperly encoded document is not really a text document at all;
nothing should be done on the basis of it.  XML's draconian error handling rule
should lead to a "fatal error", which means the rest of the document must
not be parsed.

CON: Some parsers may be relying on libraries supplied by the OS, which may
not properly signal erroneous input.  Is it too great a burden on the
parser implementor to impose this restriction?


Issue PE24:

Currently, system identifiers may or may not contain fragment identifiers
(the string beginning with "#" at the end of a URI reference).  The Recommendation
says that if a fragment identifier is present, a processor "may signal an error".
This suggests that the legitimate actions for a parser, on finding a fragment
identifier, are either to process it properly or to signal an error.
It is not clear whether the parser is allowed to simply ignore the
fragment identifier.

We are considering changing this language to say that "it is an error" to
use a fragment identifier.  This would mean that a parser may respect the
fragment identifier, signal an error, silently ignore the fragment identifier,
or even cause demons to fly out of your nose when it finds one.  (:-)).

Is this appropriate?  Are existing parsers ignoring fragment identifiers?
Should we *require* that an error be signalled?


Note: I have set the Reply-To addresses to xml-dev and to xml-editor@w...,
which is an archive of comments on the XML Rec.  Feel free to replicate
this message elsewhere, but try to preserve the Reply-Tos.

-- 

Schlingt dreifach einen Kreis um dies! || John Cowan <jcowan@r...>
Schliesst euer Aug vor heiliger Schau,  || http://www.reutershealth.com
Denn er genoss vom Honig-Tau,           || http://www.ccil.org/~cowan
Und trank die Milch vom Paradies.            -- Coleridge (tr. Politzer)

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.