At 3:55 PM -0400 4/25/04, Michael Glavassevich wrote:
The XML spec also says: "It is an *error* for a fragment identifier
(beginning with a # character) to be part of a system identifier."
What is an error? The spec defines it as: "a violation of the rules
of this specification; results are undefined. Unless otherwise
specified, failure to observe a prescription of this specification
indicated by one of the keywords MUST, REQUIRED, MUST NOT, SHALL and
SHALL NOT is an error. Conforming software MAY detect and report an
error and MAY recover from it." [1] The spec doesn't compel a parser
to detect errors (besides violations of validity constraints,
reported at user option), nor does it specify how a parser recovers
if it chooses to.
However, the SAX spec says that such errors correspond to calls to
the error() method in the registered ErrorHandler, if any. I think it
should be reported if the user has installed an error handler.
Silently throwing away data is a bad thing.
--
Elliotte Rusty Harold
elharo@xxxxxxxxxxxxxxx
Effective XML (Addison-Wesley, 2003)
http://www.cafeconleche.org/books/effectivexml
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
List: sax-devel, sax-devel@xxxxxxxxxxxxxxxxxxxxx
See: http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|