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

Re: RE: RDDL and XML element behaviors was: Re: RDDL


rddl en xml
Or even better, maybe people should stop associating namespace URIs with HTTP
URLs instead of going ahead to add more complexity and buzzword XML
technologies to an already overpopulated XML space.

For example, I've never looked at an XML document with MSFT namespaces and
wondered to myself "Hmmm, what is at the end of
urn:schemas-microsoft-com:xml-sql" or "I wonder what happens when I type
urn:schemas-microsoft-com:datatypes in my browser".

Basically this is "me too" post echoing Paul T's sentiments that created this
subthread in the first place. I really don't think "The what is the at the end
of a namespace riddle?" is a significant one to most people and for those whom
it is a significant issue I don't think RDDL is the right answer to the
question.

I sincerely believe that RDDL is a technical solution to a social problem.
Somewhere along the line people forgot that URI != HTTP URL and now RDDL is an
attempt to shoehorn yet another layer of complexity to solve a problem created
after the fact by short sightedness in the early usage of namespaces.

Now, after reading ERH's article on RDDL[0], I have a much better
understanding of what RDDL is supposed to do (someone needs to rewrite the
first few sections of that document if they want anybody besides hardcore
XML-DEVers to understand what the heck RDDL is about) and think the goal is
laudable but smacks of a complicated solution that may have a simpler answer.
Unfortunately the spec, is written in a relatively unapproachable manner[1] or
I'd offer more specificity in my criticisms. I do know that I did dislike the
assumption throughout the document that URI = HTTP URL.

[0] http://xml.oreilly.com/news/xmlnut2_0201.html#code


--
THINGS TO DO IF I BECOME AN EVIL OVERLORD #49
If I learn the whereabouts of the one artifact which can destroy me, I
will not send all my troops out to seize it. Instead I will send them
out to seize something else and quietly put a Want-Ad in the local paper.


----- Original Message -----
From: "Nicolas LEHUEN" <nicolas.lehuen@u...>
To: "'Jonathan Borden'" <jborden@m...>; "'Elliotte Rusty Harold'"
<elharo@m...>; "'Paul T'" <pault12@p...>; "'Bullard, Claude
L (Len)'" <clbullar@i...>; "'Leigh Dodds'" <ldodds@i...>;
<xml-dev@l...>
Sent: Friday, January 18, 2002 8:01 AM
Subject:  RE: RDDL and XML element behaviors was: Re:  RDDL
(was RE:  Negotiate Out The Noise)



That's why I suggest to split the spec in two : one spec trying to answer
the 'riddle' (I got it, now :) "what's at the end of a namespace URL", and
another trying to solve the serious problem of a generic way to associate
meta-data to XML document without making them crowded with DOCTYPE,
xsi:schemaLocation, stylesheet PIS (which are a bad idea, BTW) and other
corny stuff.





_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.