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

XML 3E and SAX (Re: JSR 206 and SAX)

• To: "Elliotte Rusty Harold" <elharo@m...>
• Subject: XML 3E and SAX (Re: JSR 206 and SAX)
• From: "Jeff Rafter" <lists@j...>
• Date: Thu, 19 Feb 2004 16:44:57 -0800
• Cc: "Norman Walsh" <ndw@n...>,<xml-dev@l...>,"David Megginson" <dmeggin@a...>
• References: <87znbgt3nb.fsf@n...> <40341A54.40806@a...> <87n07elu8e.fsf@n...> <p06010203bc5acccee4c1@[192.168.254.4]> <014f01c3f73a$eb5b7830$6403a8c0@ARIMATHEA> <p06010205bc5af6249b29@[192.168.254.4]>

Just so I have said it, I have this nagging feeling that something I read in
XML Third Edition impacts something I read somewhere in SAX. Has anyone else
scanned 3E under this lens? For some reason when I am trying to remember
what it was the errata that impacted the standalone declaration seemed to be
it, but the is-standalone property description seems pretty unobtrusive. The
other area of significance to the SAX specification was the changes to
encoding detection and the BOM. I remember awhile back there were questions
about whether or not SAX should report the presence of a BOM and this was
voted down. Of course, there may be nothing in 3E that impacts the SAX
specification and I am just in need of sleep.

All the best,
Jeff Rafter

• References:
  • JSR 206 and SAX
    • From: Norman Walsh <ndw@n...>
  • Re: JSR 206 and SAX
    • From: David Megginson <dmeggin@a...>
  • Re: JSR 206 and SAX
    • From: Norman Walsh <ndw@n...>
  • Re: JSR 206 and SAX
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: JSR 206 and SAX
    • From: "Jeff Rafter" <lists@j...>
  • Re: JSR 206 and SAX
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: XML publishing frameworks and software methodologies
• Next by Date: RE: XML Help
• Previous by thread: Re: JSR 206 and SAX
• Next by thread: Re: JSR 206 and SAX
• Index(es):
  • Date
  • Thread