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

RE: Can we treat XML elements and attributes as sets

• To: Michael Kay <mike@s...>, xml-dev@l...
• Subject: RE: Can we treat XML elements and attributes as sets
• From: Mukul Gandhi <mukul_gandhi@y...>
• Date: Sat, 20 Aug 2005 21:07:30 -0700 (PDT)
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Alsp4f5Xb7k8m4NLLrLBrr3BjC6lC/bz5M9v6mVbEX9vcOtEqTXLWf1o875VjdmCsoobFiJJcpCIQtKxo4kj6NOqr/Qzs0poTIKXIDMfNP2eI1XRTl5HsBeh/P38XOZcjXjsyS+KfDSN3vv7JI7K+O9oR6aa5mnlpO4tGB4tSb0= ;

Thanks Mike for clarification, and more information..
I did'nt knew namespace URIs could be null. At a
superficial level, I think namespace URIs cannot be
null in a XML document(or can they be?). I believe you
are referring null, when programming with XML
namespaces in a programming language(likely using some
APIs)?

Thanks in advance for any answers..

Regards,
Mukul

--- Michael Kay <mike@s...> wrote:

> Yes, I think it's correct - with one minor
> reservation: the XML Namespace
> recommendation insists, for some reason I have never
> understood, that names
> whose namespace URI is null are not "in a
> namespace". This leads to a great
> deal of tortuous circumlocution in other specs (such
> as the Schema
> recommendation). The model would be much simpler if
> one regarded such names
> as being in an unnamed namespace.
> 
> Michael Kay
> http://www.saxonica.com/



		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 

• Follow-Ups:
  • RE: Can we treat XML elements and attributes as sets
    • From: "Michael Kay" <mike@s...>

• Prev by Date: Re: Can we treat XML elements and attributes as sets
• Next by Date: Re: Schematron 1.6 with Jing?
• Previous by thread: Schematron 1.6 with Jing?
• Next by thread: RE: Can we treat XML elements and attributes as sets
• Index(es):
  • Date
  • Thread