• To: <sax-devel@l...>,"Elliotte Rusty Harold" <elharo@m...>
• Subject: Re: SAX survey: expected local name for non-namespace qualified elements
• From: "Rob Lugt" <roblugt@e...>
• Date: Thu, 30 May 2002 11:20:16 +0100
• Cc: <xml-dev@l...>,<xerces-j-dev@x...>
• References: <(Your message of "Tue, 28 May 2002 11:36:07 +0900.") <4.2.0.58.J.20020528113123.044b18f8@localhost> <4.2.0.58.J.20020528184428.024936f8@localhost> <3CF4DA2A.9010006@t...> <p04330102b91aaccc6808@[192.168.254.4]>

Elliotte Rusty Harold wrote
>
> consider this document with no namespaces:
>
> <document>
>    <para>
>      Hello!
>    </para>
> <document>
>
> When a parser calls startElement() or endElement() for these
> elements, is it allowed to report their local names as the empty
> string, and only provide the name as the qName argument? Or must it
> report the local names as "document" and "para"?

When I read this for the first time I assumed that local names would always
be present (when namespaces are enabled).  I can see now that the clause
"(if one is specified, both must be)" is ambiguous if the namespace URI is
empty, but I still think of an empty URI string as providing the namepace
URI - which happens to be empty.

>
> 2. If you've implemented a parser, what does your parser do?

The ElCel SAX Driver always provides a local name.  If the namespace URI is
empty (i.e. there is no default namespace), then the localName is equal to
the qName.  When namespace processing is disabled, we still provide a
localName and a qName which are identical.

Regards
~Rob

--
Rob Lugt
ElCel Technology
http://www.elcel.com/

• References:
  • SAX survey: expected local name for non-namespace qualifiedelements
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Question: Plugins in XML?
• Next by Date: Web Services Review
• Previous by thread: Re: SAX survey: expected local name for non-namespace qualifiedelements
• Next by thread: Re: SAX survey: expected local name for non-namespace qualified elements
• Index(es):
  • Date
  • Thread