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

Re: Re: URIs, concrete (was Re: Un-ask the question)

• To: David Carlisle <davidc@n...>
• Subject: Re: Re: URIs, concrete (was Re: Un-ask the question)
• From: Uche Ogbuji <uche.ogbuji@f...>
• Date: Fri, 02 Aug 2002 09:24:38 -0600
• Cc: xml-dev@l...
• In-reply-to: Message from David Carlisle <davidc@n...> of "Fri, 02 Aug 2002 11:04:27 BST." <200208021004.LAA09361@n...>
• Sender: uche.ogbuji@f...

> 
> > If your reasoning were to be followed, then the nasty SOAP and XSD
> > pattern of  non-namespaced child elements would make sense, and I
> > can't accept that. 
> 
> I made a statement about attributes (actually I just quoted one from the
> namespace spec) so i fail to see how you can infer anything about
> elements from that statement. (And I agree with you, the XSD
> default behaviour of non-namespaced elements is dire)

Oh no no no no.  Don't try to wriggle out of it.  *You* said:

"the purpose of putting an attribute (or element) into a namespace is to
ne able to refer to that attribute or element name unambiguously from
other contexts."

You threw in elements, so I showed you how your position was overgeneralized.


> > Since, as you say, the *only* reasin to give something a namespace is
> > to allow  it to be inserted willy-nilly into other vocabularies.
> 
> the namespace spec clearly states that giving something a global name
> although that provides a mechanism to refer to attributes/elements makes
> no statements about whether it is "proper usage" to do so in any
> particular case. So whether another vocabulary allows a reference
> to such an attribute is explictly not an issue here. 

Actually, this is the point I'm trying to make.  The fact that an attribute 
has a namespace doesn't suddenly make it OK to use that attribute in any other 
vocabulary, which is the logical inference that you were making.


> > This specification makes no assertions as to the proper usage of such
> > attributes. The combination of the namespace name and the attribute
> > name uniquely identifies the global attribute.

You've quoted this several times.  I've ignored it because it seems largely 
irrelevant, and to the extent relevant, it only seems to corroborate what I'm 
saying.  You seem to think otherwise.  Can you explain?


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Track chair, XML/Web Services One Boston: http://www.xmlconference.com/
Basic XML and RDF techniques for knowledge management, Part 7 - 
http://www-106.ibm.com/developerworks/xml/library/x-think12.html
Keeping pace with James Clark - http://www-106.ibm.com/developerworks/xml/libra
ry/x-jclark.html
Python and XML development using 4Suite, Part 3: 4RDF - 
http://www-105.ibm.com/developerworks/education.nsf/xml-onlinecourse-bytitle/8A
1EA5A2CF4621C386256BBB006F4CEC

• Follow-Ups:
  • Re: Re: URIs, concrete (was Re: Un-ask the question)
    • From: David Carlisle <davidc@n...>

• References:
  • Re: Re: URIs, concrete (was Re: Un-ask the question)
    • From: David Carlisle <davidc@n...>

• Prev by Date: Re: Global/Local attributes
• Next by Date: Re: Re: URIs, concrete (was Re: Un-ask the question)
• Previous by thread: Re: Re: URIs, concrete (was Re: Un-ask the question)
• Next by thread: Re: Re: URIs, concrete (was Re: Un-ask the question)
• Index(es):
  • Date
  • Thread