UDDI Core tModels

Taxonomy and Identifier Systems

 

Open Draft 23 August 2001

This version: 1.03

Latest version: 1.03

Previous version: N/A

Editor:

David Ehnebuske
Christopher Kurt

Copyright 2000 - 2002 by Accenture, Ariba, Inc., Commerce One, Inc., Fujitsu Limited, Hewlett-Packard Company, i2 Technologies, Inc., Intel Corporation, International Business Machines Corporation,  Microsoft Corporation, Oracle Corporation, SAP AG, Sun Microsystems, Inc., and VeriSign, Inc.  All Rights Reserved.

 

These UDDI Specifications (the "Documents") are provided by the companies named above ("Licensors") under the following license.  By using and/or copying this Document, or the Document from which this statement is linked, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:

 

Permission to copy, prepare derivative works based on, and distribute the contents of this Document, or the Document from which this statement is linked, and derivative works thereof, in any medium for any purpose and without fee or royalty under copyrights is hereby granted, provided that you include the following on ALL copies of the document, or portions thereof, that you use:

1.           A link to the original document posted on uddi.org.

2.           An attribution statement : "Copyright 2000 - 2002 by Accenture, Ariba, Inc., Commerce One, Inc. Fujitsu Limited, Hewlett-Packard Company, i2 Technologies, Inc., Intel Corporation, International Business Machines Corporation,  Microsoft Corporation, Oracle Corporation, SAP AG, Sun Microsystems, Inc., and VeriSign, Inc.  All Rights Reserved."

If the Licensors own any patents or patent applications that may be required for implementing and using the specifications contained in the Document in products that comply with the specifications, upon written request, a non-exclusive license under such patents shall be granted on reasonable and non-discriminatory terms. 

 

EXCEPT TO THE EXTENT PROHIBITED BY LOCAL LAW, THIS DOCUMENT (OR THE DOCUMENT TO WHICH THIS STATEMENT IS LINKED) IS PROVIDED "AS IS," AND LICENSORS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY OF THE INFORMATIONAL CONTENT, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY OR (WITH THE EXCEPTION OF THE RELEVANT PATENT LICENSE RIGHTS ACTUALLY GRANTED UNDER THE PRIOR PARAGRAPH) LICENSOR PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. Some jurisdictions do not allow exclusions of implied warranties or conditions, so the above exclusion may not apply to you to the extent prohibited by local laws. You may have other rights that vary from country to country, state to state, or province to province.

 

EXCEPT TO THE EXTENT PROHIBITED BY LOCAL LAW, LICENSORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL DAMAGES, OR OTHER DAMAGES (INCLUDING LOST PROFIT, LOST DATA, OR DOWNTIME COSTS), ARISING OUT OF ANY USE, INABILITY TO USE, OR THE RESULTS OF USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF, WHETHER BASED IN WARRANTY, CONTRACT, TORT, OR OTHER LEGAL THEORY, AND WHETHER OR NOT ANY LICENSOR WAS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some jurisdictions do not allow the exclusion or limitation of liability for incidental or consequential damages, so the above limitation may not apply to you to the extent prohibited by local laws.

Status

This document is an Open Draft defining the UDDI core tModels that represent taxonomies, and identifier systems and relationships. Comments to the editors are welcome but you are encouraged to share your views on the UDDI public mailing list (uddi-technical@yahoogroups.com).

Table of Contents

UDDI Types Taxonomy

North American Industry Classification System (NAICS) 1997 Release

United Nations Standard Products and Services Code System (UNSPSC) Version 3.1

Universal Standard Products and Services Classification (UNSPSC) Version 7.3 and beyond

ISO 3166 Geographic Taxonomy

UDDI "Other" Taxonomy

D-U-N-S Number Identifier System

Thomas Register Supplier Identifier Code System

References

UDDI Types Taxonomy

Introduction

In UDDI, tModels are used to establish the existence of a variety of concepts and to point to their technical definitions. To distinguish among various types of concept, UDDI has established this types taxonomy. tModel Publishers should categorize the tModels they publish using values from uddi-org:types to make them easy to find. Categorization is done using the usual UDDI categorization mechanism. See UDDI Version 1.0 Programmer's API Specification [1] and UDDI Version 1.0 Data Structure Reference [2] for more information on how to use taxonomies in UDDI.

Design Goals

The goal of the UDDI types taxonomy is to establish an unambiguous, simple UDDI-compatible taxonomy that distinguishes the kinds of concepts that tModels can represent.

tModel Definition

tModels:

Name: uddi-org:types

Description: UDDI Type Taxonomy

tModel UUID: uuid:C1ACF26D-9672-4404-9D70-39B756E62AB4

Categorization: categorization

Checked: Yes

Valid Values

The following constitute the identifier space for this taxonomy. The valid values are those IDs marked as being "allowed".

ID

ParentID

Allowed

Description

tModel

 

no

These types are used for tModels

identifier

tModel

yes

Unique identifier

namespace

tModel

yes

Namespace

categorization

tModel

yes

Categorization (taxonomy)

specification

tModel

yes

Specification for a Web Service

xmlSpec

specification

yes

Specification for a Web Service using XML messages

soapSpec

xmlSpec

yes

Specification for interaction with a Web Service using SOAP messages

wsdlSpec

specification

yes

Specification for a Web Service described in WSDL

protocol

tModel

yes

Protocol

transport

protocol

yes

Wire/transport protocol

signatureComponent

tModel

yes

Signature component

tModel: The UDDI type taxonomy is structured to allow for categorization of registry entries other than tModels. This key is the root of the branch of the taxonomy that is intended for use in categorization of tModels within the UDDI registry. Categorization is not allowed with this key.

identifier: An identifier tModel represents a specific set of values used to uniquely identify information. Identifier tModels are intended to be used in keyedReferences inside of identifierBsags. For example, a Dun & Bradstreet D-U-N-S Number uniquely identifies companies globally. The D-U-N-S Number taxonomy is an identifier taxonomy.

namespace: A namespace tModel represents a scoping constraint or domain for a set of information. In contrast to an identifier, a namespace does not have a predefined set of values within the domain, but acts to avoid collisions. It is similar to the namespace functionality used for XML. For example, the uddi-org:relationships tModel, which is used to assert relationships between businessEntities is a namespace tModel.

categorization: A categorization tModel is used for information taxonomies within the UDDI registry. NAICS and UNSPSC are examples of categorization tModels.

specification: A specification tModel is used for tModels that define interactions with a Web Service. These interactions typically include the definition of the set of requests and responses, or other types of interaction, that are prescribed by the service. tModels describing XML, COM, Corba, or any other services are specification tModels.

xmlSpec: An xmlSpec tModel is a refinement of the specification tModel type. It is used to indicate that the interaction with the service is via XML. The UDDI API tModels are xmlSpec tModels.

soapSpec: Further refining the xmlSpec tModel type, a soapSpec is used to indicate that the interaction with the service is via SOAP. The UDDI API tModels are soapSpe tModels, in addition to xmlSpec tModels.

wsdlSpec: A tModel for a Web Service described using WSDL is categorized as a wsdlSpec.

protocol: A tModel describing a protocol of any sort.

transport: A transport tModel is a specific type of protocol. HTTP, FTP, and SMTP are types of transport tModels.

signatureComponent: A signature component is used to for cases where a single tModel can not represent a complete specification for a Web Service. This is the case for specifications like RosettaNet, where implementation requires the composition of three tModels to be complete - a general tModel indicating RNIF, one for the specific PIP, and one for the error handling services. Each of these tModels would be of type signature component, in addition to any others as appropriate.

Example of Use

The following demonstrates how to classify a tModel as representing a taxonomy. The NAICS taxonomy, for example, is classified this way.

<tModel tModelKey=...
...
 <categoryBag>
 <!--Specify that this is a taxonomy tModel by classifying it as "categorization"
 under the uddi-org:types taxonomy -->
 <keyedReference keyName="uddi-org:types" keyValue="categorization"
 tModelKey="uuid:C1ACF26D-9672-4404-9D70-39B756E62AB4"/>
 </categoryBag>
...
</tModel>

North American Industry Classification System (NAICS) 1997 Release

Introduction

UDDI provides a mechanism that may be used by publishers to tag their businessEntities, businessServices, and tModels with information that categorizes them according to any number of taxonomies. (See UDDI Version 1.0 Programmer's API Specification [1] and UDDI Version 1.0 Data Structure Reference [2] for more information on how to use taxonomies in UDDI.) This section defines the tModel that represents the North American Industry Classification System (NAICS) taxonomy, 1997 version. The ntis-gov:naics:1997 tModel is intended to be used in connection with the UDDI categorization mechanism to categorize businessEntities, businessServices, and tModels with NAICS industry classification codes.

Design Goals

See http://www.ntis.gov or any of the UDDI operator sites for more information on the NAICS goods and services taxonomy.

tModel Definition

tModels:

Name: ntis-gov:naics:1997

Description: Business Taxonomy: NAICS (1997 Release)

tModel UUID: uuid:C0B9FE13-179F-413D-8A5B-5004DB8E5BB2

Categorization: categorization

Checked: Yes

Valid Values

See http://www.census.gov/epcd/www/naics.html or any of the UDDI operator sites to browse the list of valid NAICS 1997 release codes.

Example of Use

The following is a typical use of the NAICS taxonomy to classify a businessEntity

<businessEntity businessKey=...
 ...
 <categoryBag>
 <!-- Classify this businessEntity using the NAICS taxonomy -->
 <keyedReference keyName="Non-scheduled chartered freight air transportation"
 keyValue="481212"
 tModelKey="uuid:C0B9FE13-179F-413d-8A5B-5004DB8E5BB2"/>
 </categoryBag>
...
</businessEntity>

Note that the use of keyName aids in readability but is not required. It is the keyValue that specifies the classification.

United Nations Standard Products and Services Code System (UNSPSC) Version 3.1

Introduction

This tModel has been superceded by the Universal Standard Products and Services Classification (UNSPSC) taxonomy and, therefore, should no longer be used. It is maintained as an unchecked taxonomy so that existing registry entries that refer to it will continue to work.

UDDI provides a mechanism that may be used by publishers to tag their businessEntities, businessServices, and tModels with information that categorizes them according to any number of taxonomies. (See UDDI Version 1.0 Programmer's API Specification [1] and UDDI Version 1.0 Data Structure Reference [2] for more information on how to use taxonomies in UDDI.) This section defines the tModel that represents the UNSPSC 3.1 goods and services taxonomy, version 3.1. The unspsc-org:unspsc:3-1 tModel is intended to be used in connection with the UDDI categorization mechanism to categorize businessEntities, businessServices, and tModels with UNSPSC goods and services classifications.

Design Goals

See the ECCMA's (the taxonomy provider's) site for more information goals of the UNSPSC goods and services taxonomy.

tModel Definition

tModels:

Name: unspsc-org:unspsc:3-1

Description: Product Taxonomy: UNSPSC (Version 3.1)

tModel UUID: uuid:DB77450D-9FA8-45D4-A7BC-04411D14E384

Categorization: categorization

Checked: No

Valid Values

The valid values for this now obsolete version of UNSPSC may be derived from information maintained by the UNSPSC taxonomy's provider, ECCMA.

Example of Use

<businessEntity businessKey=... 
...
 <categoryBag>
 <keyedReference keyName="Domestic Air Cargo Transport"
 keyValue="78101501"
 tModelKey = "uuid:DB77450D-9FA8-45d4-A7BC-04411D14E384"/>
 </categoryBag>
...
</businessEntity>

Universal Standard Products and Services Classification (UNSPSC) Version 7.3

Introduction

UDDI provides a mechanism that may be used by publishers to tag their businessEntities, businessServices, and tModels with information that categorizes them according to any number of taxonomies. (See UDDI Version 1.0 Programmer's API Specification [1] and UDDI Version 1.0 Data Structure Reference [2] for more information on how to use taxonomies in UDDI.) This section defines the tModel that represents the UNSPSC goods and services taxonomy, version 7.3. The unspsc-org:unspsc tModel is intended to be used in connection with the UDDI categorization mechanism to categorize businessEntities, businessServices, and tModels with UNSPSC goods and services classifications. This tModel supercedes the UNSPSC Version 3.1 tModel, which should no longer be used.

Design Goals

See the ECCMA's (the taxonomy provider's) site for more information goals of the UNSPSC goods and services taxonomy.

tModel Definition

tModels:

Name: unspsc-org:unspsc

Description: Product and Services Taxonomy: UNSPSC (Version 7.3)

tModel UUID: uuid:CD153257-086A-4237-B336-6BDCBDCC6634

Categorization: categorization

Checked: Yes

Valid Values

See any of the UDDI operator sites to browse the list of valid UNSPSC codes.

Example of Use

<businessEntity businessKey=... 
...
 <categoryBag>
 <keyedReference keyName="Domestic Air Cargo Transport"
 keyValue="78.10.15.01.00"
 tModelKey = "uuid:CD153257-086A-4237-B336-6BDCBDCC6634"/>
 </categoryBag>
...
</businessEntity>

ISO 3166 Geographic Taxonomy

Introduction

This section defines the tModel that represents the ISO 3166 geographic taxonomy, a domain of values used to provide geographic categorization of businesses and services within the UDDI registry. This categorization scheme assists in supporting UDDI inquiries for businesses or services that serve specific geographic areas.

Design Goals

The design goal for this tModel is to provide standards-based, large-grained taxonomy to represent geographical locations for the purpose of indicating that businesses or services serve particular geographic areas. It is acknowledged by the authors that there are many other alternative taxonomies with similar, or richer geographic information.

tModel Definition

The values in this geographic taxonomy are defined in ISO specifications 3166-1 and 3166-2 [3]. Also included are update newsletters that have been distributed as addition to the set of values described in the original specifications. From the value set, a relatively flat hierarchy is derived for use in conjunction with the UDDI registry. The following releases have been included in the data set:

A summary of the UDDI registry entry for the ISO 3166 standard is provided here.

tModels:

Name: uddi-org:iso-ch:3166-1999

Description: ISO 3166-1:1997 and 3166-2:1998. Codes for names of countries and their subdivisions. Part 1: Country codes. Part 2: Country subdivision codes. Update newsletters include ISO 3166-1 V-1 (1998-02-05), V-2 (1999-10-01), ISO 3166-2 I-1 (1998).

tModel UUID: uuid:4E49A8D6-D5A2-4FC2-93A0-0411D8D19E88

Categorization: categorization

Checked: Yes

Valid Values

See the UDDI Web site for a list of the valid iso-ch:3166-1999 values. This file consists of four tab-separated columns of text in UTF-8 format. Except for the first line which is a header, each line in the file gives information about one of the categories in the taxonomy. The first column, labelled "Key" is the identifier for the category. Each Key is a valid value for the taxonomy.  The second column, labelled, "Parent" contains the Key for the more general category under which this category fits. The category named "World" has itself as a Parent to indicate that it is the most general categorization in the taxonomy. The third column, "Name" is the UTF-8 English name of the category. The fourth column, "Current" is a "1" if the category is recommended for use in new categorizations. It is "0" if its use has been deprecated. No other values may appear in the Current column.

Any valid values, current or deprecated, may be used for inquiries, but only current values should be used to make new classifications.

Example of Use

The following is a typical business registration referencing the uddi-org:iso3166 tModel.

<businessEntity businessKey=...
 ...
 <categoryBag>
 <!-- Categorize this businessEntity as serving California using the ISO 3166
 taxonomy -->
 <keyedReference keyName="California, USA"
 keyValue="US-CA"
 tModelKey="uuid:4E49A8D6-D5A2-4FC2-93A0-0411D8D19E88"/>
 </categoryBag>
...
</businessEntity>

UDDI "Other" Taxonomy

Introduction

Usually, taxonomies in UDDI are defined by registering a new tModel to represent the taxonomy, but sometimes such fomality is overkill. The UDDI "Other" Taxonomy provides a way of informally defining any number of unchecked taxonomies each consisting of a namespace identifier and an associated set of category values.

Design Goals

Provide a simple, lightweight means for establishing and using unchecked UDDI taxonomies. Such taxonomies are generally fairly simple and often of interest only to a small number of people. Complex taxonomies or broadly interesting taxonomies should be defined by registering a new tModel which is the formal means of documenting the meaning and intended use of your taxonomy.

tModel Definition

tModels:

Name: uddi-org:misc-taxomony

Description: Special taxonomy consisting of namespace identifiers and the keywords associated with the namespaces

tModel UUID: uuid:A035A07C-F362-44dd-8F95-E2B134BF43B4

Categorization: categorization

Checked: No

Valid Values

This taxonomy in UDDI behaves differently than do any of the other taxonomies. Like other taxonomies, this taxonomy is used in keyedReference elements to categorize the entities. Unlike other taxonomies, in the uddi-org:misc-taxonomy both the keyName and the keyValue attributes of keyedReference elements are semanitcally meaningful. The keyName identifies a particular value set and the keyValue specifies the value within that value set. With other taxonomies, the keyName plays no semantic role it is essentially commentary. This difference is reflected in the UDDI inquiry APIs: When a keyedReference containing a reference to the general_keyword taxonomy appears in an inquiry, the keyNames count.

Although UDDI puts no limitations on the value of keyName attributes, keyNames used with the general_keywords taxonomy should be URNs with what the W3C calls "an institutional commitment to persistence" in a domain name space you own. Following this convention will help avoid name collisions.

UDDI places no limitations on the value of keyValue attributes. keyValues may be whatever set of values you choose for your taxonomy.

Example of Use

In The Analytical Language of John Wilkins (translated from the Spanish El idioma analtico de John Wilkins by Lilia Graciela Vzquez; edited by Jan Frederik Solem with assistance from Bjrn Are Davidsen and Rolf Andersen) Jorge Luis Borges discusses the problems inherent to any system of classification. The "ambiguities, redundancies and deficiencies remind us of those which doctor Franz Kuhn attributes to a certain Chinese encyclopaedia entitled Celestial Empire of Benevolent Knowledge. In its remote pages it is written that the animals are divided into: (a) belonging to the emperor, (b) embalmed, (c) tame, (d) sucking pigs, (e) sirens, (f) fabulous, (g) stray dogs, (h) included in the present classification, (i) frenzied, (j) innumerable, (k) drawn with a very fine camelhair brush, (l) et cetera, (m) having just broken the water pitcher, (n) that from a long way off look like flies."

While this taxonomy has been widely referred to, it turns out that Borges probably made the whole thing up. Legitimate or bogus, the taxonomy certainly makes his point: "[I]t is clear that there is no classification of the Universe not being arbitrary and full of conjectures."

For some unknowable reason, Celestial Animals (celestialanimals.com, a completely fictitious outfit) is organized internally using this classification system, one division per classification. (Division "m" is very small.) It wishes to categorize the businessServices it offers according to the division that offers it, and, of course, it wants to use the Celestial Empire taxonomy to do so. Since the classification is only of interest to Celestial Animals, it is decided that the UDDI "other" taxonomy approach will be used. The urn "urn:celestialanimals-com:taxonomies:animals" is chosen to represent the taxonomy. The Tame Division and the Fabulous Division both have catalog browsing businessServices. They appear as follows:

 <businessServices>
 <businessService>
 <name>
 Celestial Animals Tame Animal Catalog Service
 </name>
 <description xml:lang="en">
 Search our tame animals catalog on line
 </description>
 <bindingTemplates>
 <bindingTemplate>
 <accessPoint URLType="https">
 https://celestialanimals.com/tame/catalog.html
 </accessPoint>
 <tModelInstanceDetails>
 <tModelInstanceInfo tModelKey="UUID:68DE9E80-AD09-469D-8A37-088422BFBC36">
 </tModelInstanceInfo>
 </tModelInstanceDetails>
 </bindingTemplate>
 </bindingTemplates>
 <categoryBag>
 <keyedReference 
tModelKey="UUID:uuid:CD153257-086A-4237-B336-6BDCBDCC6634" 
keyName="UNSPSC: Livestock" keyValue="10.10.15.00.00"/>
 <keyedReference 
tModelKey="UUID:A035A07C-F362-44dd-8F95-E2B134BF43B4"
 keyName="urn:celestialanimals-com:taxonomies:animals" keyValue="c"/>
 </categoryBag>
 </businessService>
 <businessService>
 <name>
 Celestial Animals Fabulous Animal Books Catalog Service
 </name>
 <description xml:lang="en">
 Search our tame animals catalog on line
 </description>
 <bindingTemplates>
 <bindingTemplate>
 <accessPoint URLType="https">
 https://celestialanimals.com/fabulous/catalog.html
 </accessPoint>
 <tModelInstanceDetails>
 <tModelInstanceInfo tModelKey="UUID:68DE9E80-AD09-469D-8A37-088422BFBC36">
 </tModelInstanceInfo>
 </tModelInstanceDetails>
 </bindingTemplate>
 </bindingTemplates>
 <categoryBag>
 <keyedReference 
tModelKey="CD153257-086A-4237-B336-6BDCBDCC6634" 
keyName="UNSPSC: Picture or drawing or coloring books for children" keyValue="55101507"/>
 <keyedReference
 tModelKey="UUID:A035A07C-F362-44dd-8F95-E2B134BF43B4"
 keyName="urn:celestialanimals-com:taxonomies:animals" keyValue="f"/>
 </categoryBag>
 </businessService>
 </businessServices>

D-U-N-S Number Identifier System

Introduction

UDDI provides a mechanism that may be used by publishers to tag their businessEntities, businessServices, and tModels with information that identifies them according to any number of identifier systems. (See UDDI Version 1.0 Programmer's API Specification [1] and UDDI Version 1.0 Data Structure Reference [2] for more information on how to use identifier systems in UDDI.) This section defines the tModel that represents the D-U-N-S Number identifier system. The D-U-N-S tModel is intended to be used in connection with the UDDI identification mechanism to identify businessEntities and tModels with D-U-N-S numbers.

Note that this tModel is initially registered as part of the UDDI core tModels. At some point custody of this tModel is expected to be transferred to the Dun & Bradstreet publisher account.

Design Goals

For more information on the D-U-N-S Number identifier system, see http://www.dnb.com.

tModel Definition

tModels:

Name: dnb-com:D-U-N-S

Description: Dun & Bradstreet D-U-N-S Number

tModel UUID: uuid:8609C81E-EE1F-4D5A-B202-3EB13AD01823

Categorization: identifier

Checked: No

Valid Values

D-U-N-S Numbers are assigned by Dun & Bradstreet. See http://www.dnb.com.

Example of Use

Identify the IBM registry entry as being IBM's by tagging it with the appropriate D-U-N-S Number.

<businessEntity businessKey=... 
...
 <identifierBag>
 <keyedReference keyName="IBM Corporation"
 keyValue="00-136-8083"
 tModelKey = "uuid:8609C81E-EE1F-4D5A-B202-3EB13AD01823"/>
 ...
 </identifierBag>
...
</businessEntity>

Thomas Register Supplier Identifier Code System

Introduction

UDDI provides a mechanism that may be used by publishers to tag their businessEntities and tModels with information that identifies them according to any number of identification systems. (See UDDI Version 1.0 Programmer's API Specification [1] and UDDI Version 1.0 Data Structure Reference [2] for more information on how to use identifier systems in UDDI.) This tModel represents the Thomas Register supplier identifier code system for use with that mechanism.

Note that this tModel is initially registered as part of the UDDI core tModels. At some point custody of this tModel is expected to be transferred to the Thomas Register publisher account.

Design Goals

See http://www.thomasregister.com for more information on the Thomas Register supplier identifier code system.

tModel Definition

tModels:

Name: thomasregister-com:supplierID

Description: Thomas Registry Suppliers

tModel UUID: uuid:B1B1BAF5-2329-43E6-AE13-BA8E97195039

Categorization: identifier

Checked: No

Valid Values

The value of keyValue in a keyedReference that refers to this tModel should be a valid Thomas Register supplier ID number issued to the publisher of the businessEntity or tModel in question. See www.thomasregister.com.

Example of Use

Here we identify the businessEntity for Microsoft with the Microsoft Business Solutions Group Thomas Register supplier ID, 43038249.

<businessEntity businessKey=...
...
 <identifierBag>
 <keyedReference keyName="thomasregister-com:supplierID Microsoft Business Solutions Group"
 keyValue="43038249"
 tModelKey="uuid:B1B1BAF5-2329-43E6-AE13-BA8E97195039"/>
 ...
 </identifierBag>
...
</businessEntity>

References

[1] uddi.org, " UDDI Version 1.0 Programmer's API Specification"

[2] uddi.org, "UDDI Version 1.0 Data Structure Reference"

[3] ISO 3166 Maintenance Agency Web Site: http://www.din.de/gremien/nas/nabd/iso3166ma/

Editor's Addresses

David Ehnebuske
IBM Corporation
11400 Burnet Road
Austin, TX 78528
Email: davide@us.ibm.com

Christopher Kurt
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Email: ckurt@microsoft.com