OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] Re: URIs, concrete

[ Lists Home | Date Index | Thread Index ]

Maybe he is right, maybe he's wrong. The fact is that there are too many apps out there to break over what is primarily an aesthethics issue. 

	-----Original Message----- 
	From: Uche Ogbuji [mailto:uche.ogbuji@fourthought.com] 
	Sent: Wed 7/31/2002 2:51 PM 
	To: jborden@attbi.com 
	Cc: xml-dev@lists.xml.org; Simon St.Laurent 
	Subject: Re: [xml-dev] Re: URIs, concrete 
	
	

	> Simon St.Laurent wrote:
	>
	> [[
	> The namespaces specification made a simple but horrid
	> mistake in failing to recognize the close relationship
	> between an attribute and its containing element.  That
	> there is a difference between:
	>
	> <x:foo x:bar="bogus"/>
	>
	> and:
	>
	> <x:foo bar="bogus"/>
	>
	> seems like yet another consequence of a disastrous
	> specification.  ... It's time to start fixing stuff
	> instead of just letting bad decisions perpetuate
	> themselves.  In practice, I really doubt that this will
	> break ANY applications.
	> ]]
	>
	> It has been generally acknowledged that you are correct
	> in that there _ought not_ be such a distinction but the
	> problem is that changing the specification at this stage
	> of the game, actually would break any number of real
	> world programs e.g.
	>
	> <xsl:template match="x:foo[@x:bar]"> ...
	>
	> now perhaps such XSLT could be recognized and auto-
	> xformed into:
	>
	> <xsl:template match="x:foo[@bar]"> ...
	>
	> but I'm sure that I've written something like the above
	> any number of times.
	
	Well, AFAIK, the only spec that enshrines the silly
	
	<x:foo x:bar/>
	
	Practice is the new RDF syntax.  I think this was an astonishingly bad idea,
	and I've railed about it at length on www-rdf-interest.
	
	If such a change in XMLNS breaks such already broken specs, personally, I
	would shed nary a tear.  The Right Thing is the Right Thing.  That's all.
	
	BTW, I'd like to see technical reasoning from anyone who says that Simon is
	wrong on the unprefixed attribute issue.  I've only heard loud declarations
	that he is wrong, without any backing.  Then again, I've only kept one eye on
	this thread lately.
	
	
	--
	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
	
	
	
	-----------------------------------------------------------------
	The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
	initiative of OASIS <http://www.oasis-open.org>
	
	The list archives are at http://lists.xml.org/archives/xml-dev/
	
	To subscribe or unsubscribe from this list use the subscription
	manager: <http://lists.xml.org/ob/adm.pl>
	
	





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS