The UDDI web site is not longer accepting new posts. Information on this page is preserved for legacy purposes only.

Revision of tModels from Tue, 2006-10-31 23:11

tModels are core components of UDDI. tModels represent unique concepts or constructs and are used to describe compliance with a specification, a concept, a category or identifier system, or a shared design. Each tModel should contain an overviewURL, which references a document that describes the tModel and its use in more detail.

Specification tModels are used to represent service type definitions, that is, reusable features of Web services. Web service registrations reference specification tModels in order to indicate their compliance with the service type definition..

Category systems and identifier systems tModels, together known as "value sets", represent another important use of tModels. These enable the categorization and identification of entities registered in UDDI in accordance to these value sets. The ability to attribute metadata to providers and services registered in UDDI, and then run queries based on that metadata is absolutely central to the purpose of UDDI at both design time and run time.

While these tModels can be published in a UDDI registry, promulgating their existence is also important. The OASIS UDDI Specification Technical Committee wants to encourage and promulgate common tModels promoted by standards groups and consortiums.

View currently published tModels.

Registering tModels with OASIS

The registration of tModels with OASIS is limited to tModels that represent a well-known concept and/or are owned by a well-known standards group, an industry vertical or a consortium (note that "well-known" may be limited to an industry, a geographical region or other contexts).

The tModel must be published at one of the UBR's nodes by either an individual who is affiliated with the author(s) of the tModel or was granted the permission to publish it on behalf of the author(s). To register as a publisher, please visit the OASIS Register page.

Technically, the tModel should follow basic recommendations and best practices for UDDI registrations. Therefore, it must contain:

  • A name, formatted as a URI
  • At least one description
  • At least one of overviewDoc/description or overviewDoc/overviewURL that describes the tModel's meaning in more detail. In case of an overviewURL, the URL must resolve to a document in a well-known format.
  • A categoryBag/keyedReference with the tModelKey of the UDDI Types category system and a keyValue that corresponds to the tModel's actual type

It should also:

  • Contain as many categories and identifiers related to it
  • Be referenced by a tModel if this represents its predecessor version. This is established by using the isReplacedBy identifier system.

Requesting registration with OASIS

tModel registration requests should be sent to the OASIS mailing list at In order to be considered, the tModel needs to have been published in the UBR and the request must include the following information:

Information items required with the request


tModel Name


tModel Description

Industry Category System: NAICS (1997 Release)

Registering Organization

UDDI Business Registry

Registrants' E-mail Address

Overview Document URL

v2 tModel Key


v3 tModel Key

The OASIS UDDI Specification Technical Committee will validate requests against above criteria and, once accepted, will post the tModel information to this page. Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I