W3C home > Mailing lists > Public > www-archive@w3.org > February 2007


From: Paul Denning <pauld@mitre.org>
Date: Mon, 26 Feb 2007 17:28:13 -0500
Message-Id: <>
Message-Id: <>
To: www-archive@w3.org

I sent a few tModels to the www-archive list as attachments.

This email points to these attachments and explains what they are.

They were previously published to the UDDI Business Registry (UBR).


[1] is a taxonomy tModel for a RDDL taxonomy.

The idea is that UDDI tModels would point to RDDL documents.  In 
other words, you can use UDDI to register RDDL documents.  You use 
the RDDL taxonomy to categorize the tModels that point to the RDDL 
documents.  You can search UDDI for documents categorized using this 
taxonomy.  Use of this taxonomy is discussed further at [6].

[6] http://lists.oasis-open.org/archives/uddi-spec/200310/msg00113.html

After I published [1] to UBR, Ann Thomas Manes suggested [7] two more 

[7] http://lists.oasis-open.org/archives/uddi-spec/200310/msg00110.html

I published the tModels for these taxonomies to the UBR, and now 
these tModels can be found at [2] and [3].

[2] is a rddl:nature "taxonomy".  The idea is that you create a 
tModel for a document.  In the categoryBag of that tModel, you use 
the rddl:nature taxonomy with a keyValue that is the URI that 
identifies the nature of document.  The overView URL of the tModel 
would point to the document.

Likewise, [3] is a rddl:purpose "taxonomy".  The same tModel would 
include a keyedReferrence in the categoryBag where the keyValue is 
the URI that identifies the purpose of the document (pointed to by 
the overviewURL).

In other words, you register a document in UDDI using a tModel whose 
categoryBag includes the nature and purpose of the document.  The 
overviewURl of this tModel points to the document.

Both the nature [3] and purpose [3] taxonomies are open-ended and 
unchecked.  That is, the UDDI registry will allow any value for the 
keyValue attribute when using these taxonomies.  There is no central 
registry of "official" natures and purposes.

Note that given a RDDL document, it would be straight forward to 
automate the generation of UDDI tModels for every @href in the 
RDDL/XHTML document and use the value of the rddl:nature and 
rddl:purpose as keyValues with the respective tModelKeys for the 
nature and purpose taxonomies.

Likewise, if you have tModels using these taxonomies, it is 
straightforward to automate generation of an XHTML/RDDL document.

I also sent some examples to www-archive [4][5].

[4] is an example of registering a RDDL document in UDDI.  The RDDl 
document happens to be http://www.rddl.org/natures/ .  This example 
does not use the nature and purpose taxonomies, but it does use the 
RDDL taxonomy [1] to simply point out that the tModel refers to a 
RDDL document (note keyValue="rddlSpec").  You would search UDDI to 
find RDDL documents in a manner similar to that for searching UDDI 
for WSDL documents.  For WSDL, tModels use keyValue="wsdlSpec".  For 
RDDL, tModels use keyValue="rddlSpec".

[5] is another example for a different RDDL 
document:  http://www.tbray.org/tag/rddl4.html

When I get a chance, I'll update the RDDL "taxonomy document" that I 
use to describe the RDDL taxonomy [8].


Just as RDDL is a suitable format for use as a "namespace document", 
RDDL is also a suitable format for use as a "taxonomy document".

Received on Monday, 26 February 2007 22:28:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:43:05 UTC