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

Re: Re: [Sax-devel] Showstopper issue with new Attribute text

• To: David Megginson <dmeggin@a...>
• Subject: Re: Re: [Sax-devel] Showstopper issue with new Attribute text
• From: "Emmanuil Batsis (Manos)" <mbatsis@n...>
• Date: Wed, 17 Mar 2004 17:47:48 +0200
• Cc: XML Developers List <xml-dev@l...>,SAX Developers' List <sax-devel@l...>
• In-reply-to: <405864E7.3090505@a...>
• Organization: Netsmart S.A., Greece
• References: <OF24BFF179.96E54E23-ON85256E54.0050C5B0-85256E54.0051D5E1@c...><p06010200bc7630593567@[192.168.254.4]> <405864E7.3090505@a...>
• Reply-to: mbatsis@n...
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)Gecko/20040113

David Megginson wrote:
> c) an attribute with the Namespace URI "http://www.w3.org/2000/xmlns/" 
> and the local name "xmlns".


If {a,b,c} is all there is, I vote for b. That way, declarations will be 
consistent whether default or not. Both xmlns and xmlns:foo should give 
the same namespace URI "http://www.w3.org/2000/xmlns/" while the latter 
should also give the local name "foo". Plain xmlns declarations should 
give a null local name IMHO.

Can I have an exclude-ns-declaration-attrs feature with that please?

If it counts to anything, I'd preffer a change in the interfaces (i.e. a 
new SAX version) instead of the above. Adding signatures that include ns 
declarations in a new collection as a parameter would be a clean 
solution. One would be able to choose what version of the events to use...

-- 
Manos Batsis

     _  __    __                    __
    / |/ /__ / /____ __ _ ___ _____/ /_
   /    / -_) __(_-</  ' Y _ `/ __/ __/
  /_/|_/\__/\__/___/_/_/_|_,_/_/  \__/


http://www.netsmart.gr
mailto:mbatsisSPAM_TRAP@n...
tel:+302103240940
http://forte.netsmart.gr/foaf/manos_foaf.rdf

• Follow-Ups:
  • Re: Re: [Sax-devel] Showstopper issue with new Attribute text
    • From: "Emmanuil Batsis (Manos)" <mbatsis@n...>

• References:
  • Re: [Sax-devel] Showstopper issue with new Attribute text
    • From: David Megginson <dmeggin@a...>

• Prev by Date: qName/localName confusion
• Next by Date: Re: qName/localName confusion
• Previous by thread: RE: qName/localName confusion
• Next by thread: Re: Re: [Sax-devel] Showstopper issue with new Attribute text
• Index(es):
  • Date
  • Thread