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

Re: namespaces redux (was: Re: [XML Schema]Here's ho

• From: Andrew Welch <andrew.j.welch@gmail.com>
• To: "Costello, Roger L." <costello@mitre.org>
• Date: Tue, 16 Oct 2012 11:47:35 +0100

>> 3. Avoid using URLs, the globally unique benefit
>> is far outweighed by the confusion cost
>
> Are you recommending that URNs be used rather than URLs?

I'm advocating simple strings for simple cases, for example for a
config file someone might be tempted to use:

xmlns:c="http://mycomp.com/someproduct/v1.1/config/"

whereas they could just do:

xmlns:c="config"

- it will never need to change
- there is no confusion if something exists at the end of the url, or
if the domain has to actually exist.
- there is no confusion around a trailing slash
- in XPath 3.0 you can have nice short self contained xpaths.
- its easy to remember
- the markup can be reused as its not associated with some product
- it still allows embedding of other markup, or this markup to be
embedded elsewhere

> If yes, doesn't that eliminate the ability to use things such as RDDL?

I don't know RDDL I'm afraid.

> XML Schema uses URLs for namespaces, as does XSLT. Do you believe that to be a mistake?

The dates were a mistake, and (I think) they should really have a
trailing slash, and they aren't the easiest to remember so unless you
have tool support or know them off by heart you need to look them
up.... but other than that for a global spec it's hard to argue
against a url.

> What do you mean by "the confusion cost"?

Hopefully the above bullets covers it, I can't think of any more for now.



-- 
Andrew Welch
http://andrewjwelch.com

• Follow-Ups:
  • Re: namespaces redux (was: Re: [XML Schema]Here's how to empower instance document authors to create their own rootelement)
    • From: Liam R E Quin <liam@w3.org>
  • Re: namespaces redux
    • From: David Carlisle <davidc@nag.co.uk>
  • Re: namespaces redux
    • From: Michael Sokolov <sokolov@ifactory.com>

• References:
  • [XML Schema] Here's how to empower instance document authors tocreate their own root element
    • From: "Costello, Roger L." <costello@mitre.org>
  • Re: [XML Schema] Here's how to empower instance documentauthors to create their own root element
    • From: Timothy Cook <timothywayne.cook@gmail.com>
  • Re: [XML Schema] Here's how to empower instance documentauthors to create their own root element
    • From: "Christopher R. Maden" <crism@maden.org>
  • Re: [XML Schema] Here's how to empower instance documentauthors to create their own root element
    • From: John Cowan <cowan@mercury.ccil.org>
  • Re: [XML Schema] Here's how to empower instance documentauthors to create their own root element
    • From: "Christopher R. Maden" <crism@maden.org>
  • Re: [XML Schema] Here's how to empower instance documentauthors to create their own root element
    • From: Liam R E Quin <liam@w3.org>
  • Re: [XML Schema] Here's how to empower instance documentauthors to create their own root element
    • From: "Christopher R. Maden" <crism@maden.org>
  • namespaces redux (was: Re: [XML Schema] Here's how toempower instance document authors to create their own root element)
    • From: Amelia A Lewis <amyzing@talsever.com>
  • Re: namespaces redux (was: Re: [XML Schema]Here's how to empower instance document authors to create their own root element)
    • From: Andrew Welch <andrew.j.welch@gmail.com>
  • RE: namespaces redux (was: Re: [XML Schema]Here's how to empower instance document authors to create their own rootelement)
    • From: "Costello, Roger L." <costello@mitre.org>