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

RE: [Sax-devel] Re: SAX survey: expected local name for non-namespace q

• To: <sax-devel@l...>
• Subject: RE: [Sax-devel] Re: SAX survey: expected local name for non-namespace qualified elements
• From: "Simon St.Laurent" <simonstl@s...>
• Date: Sun, 02 Jun 2002 16:09:52 -0400
• Cc: <xerces-j-dev@x...>, <xml-dev@l...>
• In-reply-to: <NDBBKAIFOLAGCAFIGOJJGEKPCMAA.yuval@b...>
• References: <3CFA6CEF.5060706@p...>

At 12:42 PM 6/2/2002 -0700, Yuval Oren wrote:
>Regardless of what's more natural, at this point doing anything other than
>sticking with the current specification would be pointless. Take this
>document:
>
><my:doc/>
>
>With namespace processing off, SAX2 compliant parsers can provide a
>localName value of either "" or "doc", while qName must be "my:doc". If this
>were changed in a SAX 2.1 release, 2.1-compliant parsers would always
>provide a localName value of "my:doc". That would bring us back to square
>one: you can't rely on localName when namespace processing is off.

And my point is that the localName is "my:doc" and the QName is meaningless 
in this case.

It's nice to realize how inflexible a parameter-based API can be, I suppose.

Simon St.Laurent
"Every day in every way I'm getting better and better." - Emile Coue

• Follow-Ups:
  • Re: RE: [Sax-devel] Re: SAX survey: expected local name for non-namespace qualified elements
    • From: Ronald Bourret <rpbourret@r...>

• Prev by Date: Re: The sky is falling! XML's dirty secret! Go back! It's a trap!
• Next by Date: Re: [Sax-devel] Re: SAX survey: expected local name for non-namespace qualified elements
• Previous by thread: Re: The sky is falling! XML's dirty secret! Go back! It's a trap!
• Next by thread: Re: RE: [Sax-devel] Re: SAX survey: expected local name for non-namespace qualified elements
• Index(es):
  • Date
  • Thread