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] Obtaining a Namespace or Defining a URN.

[ Lists Home | Date Index | Thread Index ]

To obtain a namespace, all you need to do is create a URI that is under
your control. No registration (or anything else) needed for the
namespace, although registration might be needed for the URI.

For example, suppose you wanted a namespace to identify elements and
attributes in the Arthur Colman Markup Language (ACML). Since
drybridge.com is already under your control (through a separate
registration process), you could create a URL and use it as a namespace


(No, it doesn't need to point to anything. You just need a unique

Two other notes. First, I'm not sure what namespaces have to do with
identifying parties in a transaction. These are completely separate
things. Second, whether or not URIs need to be registered and how to go
about doing that depends on the type of URI. You'll have to poke around
Google to find information on how to do it -- I seem to recall the W3C
has a paper about this.

-- Ron

Arthur Colman wrote:
> How does one obtain a Namespace? How does one formally register a URI?
> The context of my question is twofold. When establishing an ebXML CPA
> you are directed to provide a CPAId that identifies both the From and To
> Parties and is a URI. I'd also want to enable some uniqueness in this
> process so ideally one would want to use some sort globla identifier.
> Now the 'oid' domain of 'uri's does provide me with the ability to get a
> number that I could use to identify Trading Partners.
> However, this does not solve my other problem which is that I would like
> to provide guidance to the users of the papiNet standard (for
> communications within the Paper Manufacturing Verticle Industry) as to
> what are agreed to enumerations of types and other codes that are used
> in the SOAP-ebXML MessageHeader, etc.


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

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