[Home] [By Thread] [By Date] [Recent Entries]

  • To: "Karl Waclawek" <karl@w...>, <xerces-j-dev@x...>, <sax-devel@l...>, <xml-dev@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 10:55:36 -0400
  • In-reply-to: <001201c20a45$3f445820$0207a8c0@karl>
  • References: <" <4.2.0.58.J.20020528113123.044b18f8"@localhost><4.2.0.58.J.20020528184428.024936f8@localhost><3CF4DA2A.9010006@t...><p04330102b91aaccc6808@[192.168.254.4]><3CF5456C.4040108@p...><3CF559FB.9050008@u...><OF14B5085A.90DE2214-ON86256BCA.00592DAC@r...><3CF7CC84.1050305@u...><4.2.0.58.20020602101233.00a3fe58@p...>

At 10:53 AM 6/2/2002 -0400, Karl Waclawek wrote:
>Simon St.Laurent wrote:
>
> > If "namespace processing is off and we've never heard of namespaces", then
> > we've never heard of QNames either.  If you insist on going this route,
> > you'd better change the API to remove the notion of QName when namespace
> > processing is off.  "Local name" might at least mean "the name local to 
> the
> > element" in cases without any understanding of namespaces.
>
>I understand it the same way. The confusion in this thread really is:
>if NS processing is off, then which should really represent the
>element name - qName or localName? I agree with you that localName is
>the more natural candidate.

I'm also not certain that we want to encourage developers to look to qName 
for anything other than prefix-retrieval in any event.  I keep hearing of 
developers who rely solely on qName whatever the status of 
namespace-processing, and I guess it works for now...

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


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member