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

RE: Musing over Namespaces

• From: "Didier PH Martin" <martind@n...>
• To: "Don Park" <donpark@d...>,<xml-dev@i...>
• Date: Fri, 17 Dec 1999 13:51:11 -0500

Hi Don
Don Said:
What if the registry was a distributed semantic network?
If the problem could be solved, wouldn't it be worth
building it?  Note that this is not the way BizTalk and
XML.org schema repositories work.

Didier reply:
Right ON!!

I think this could be effectively a good way to have both name space and
schemas documented.

Let's see a practical example since I am precisely working on that this week
(among other things :-)

I created a name space for the dynamic DNS. All Dynamic DNS requests and
responses are transformed respectively into URLs and XML document. For
instance to add a new sub domain to a particular domain you send a HTTP/Get
or HTP/post with the request URL and receive an XML document about the new
inscription, and so on and so forth for all the request/response.

The name space is called DDNS. Today, if I follow the specs I would
assocaite the name space to an empty URI or do like W3C is doing for some of
its own name space URIs, have an HTML page pointed by the URI.

But, not staisfied with such half solution, I tried something: topic maps.
As we all know, do we? topic maps are composed of topic elements and a topic
element contains both names and an extended link (if you map the Hytime link
to xlink). So, the solution was simple, The name space URI is pointing to a
topic map document. This document has for main topic the ddns name space.
The extended link itself points to different specifications used to create
this name space. This could include also schemas.

So, if the name space URI would be use for something useful, it could point
to a topic map document, this latter provide information about the name
space seen as a topic.

But Didier, what did we gained? he said with some incredulity.

Simple, a machine can decode a topic map document but not necessarily an
HTML page. Moreover, if we all agree on a convention about the document
structure, then a processor could easily retreive the schema, humans the
written documentation and even have this name space associated to other ones
by relationship like "is_derived_from" is "is-part_of" or more simply with
set relations and tagging like "finance", "system", "network" etc...

Do others are interested to have meaninful name space? if yes, we can
publish a paper providing a recommendation on how to document a name space.
I'll start the first draft and post it.

Cheers
Didier PH Martin
----------------------------------------------
Email: martind@n...
Conferences:
Web New York (http://www.mfweb.com)
Book to come soon: XML Pro published by Wrox Press
Products: http://www.netfolder.com


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • RE: Musing over Namespaces
    • From: "Don Park" <donpark@d...>

• References:
  • RE: Musing over Namespaces
    • From: "Don Park" <donpark@d...>

• Prev by Date: RE: Musing over Namespaces
• Next by Date: RE: Musing over Namespaces
• Previous by thread: RE: Musing over Namespaces
• Next by thread: RE: Musing over Namespaces
• Index(es):
  • Date
  • Thread