UDDI Version 2.0 API schema. Release candidate 1, review draft 3 Returned on output, ignored in input. A persons name that is associated with the publication of registered data. Multi-use. Identifies the bindingKey value associated with a bindingTemplate. On save, empty value implies that a new bindingTemplate key is to be assigned. Multi-use. Identifies the businessKey value associated with a businessEntity. On save, empty value implies that a new businessEntity key is to be assigned. Signifies the UDDI registry software version number. On input, signifies the UDDI version understood by the requesting caller. The name part of a name-value pair. In a keyedReference, these are purely descriptive except when used with the uddi-org:general tModell, where they are used as the Name part of a name value pair. In address, these are addressLine code-set field names The value part of a name-value pair. This is the value associated with the context specified by the tModelKey value. In address, these are qualifierss on the field name. Used on input to limit the maximum result size returned from inquiry API messages. Ignored on input. Identifies the UDDI registry that supplied the data (top level message attribute) and the UDDI registry where the data is mastered (entity level use). Multi-use. Identifies the serviceKey value associated with a businessService. On save, empty value implies that a new businessService key is to be assigned. Used to convey application specific rules. Typically a URN identifying the application manufacturer, application, and version. Ex. "urn:foo-com:foocontactMgr:v-1-0" A reference to a tModel. Usually used to represent the context to understand the keyName and keyValue values. Used on output only. Signifies that results returned do not reflect the complete result set possible. Used to specify the transport type associated with a bindingTemplate. If a given web service or entry point represented by a binding has multiple possible transports, a bindingTemplate should be added to the same businessService for each transport, repeating all of the same information except the transport type and the accessPoint or hostingRedirector pointer. Descriptive attribute. Used to convey the intended use. Suggested values are URN identifying the intended use. Ex. "urn:contact:technical" Data: present when a service is directly accessible at a particular address (e.g. URL, etc). Mutually exclusive with hostingRedirector. An address. Use the useType attribute to signify purpose. Use the sortCode attribute to signify associated software make/product/version. Use the tModelKey to signify the context or namespace of keyName/keyValue markeup on individual addressLine elements. A part of an address. Order of addressLine elements is not lax. Use the optional keyName keyValue attributes to specify field specific parsing hints. These should be used in conjunction with the optional tModelKey on the address structure to identify the namespace or context of the address element. These field hints are not validated by UDDI registries. This is a report back to the publisher of assertions - the status indicates whether the handshake conditions (both key owners have asserted the same facts) have been satisfied. Only symmetric relationship types require the agreement between parties. See the UDDI V2 API specification for valid values. This structure is used in all publishing API messages. It holds an authentication token value. This is the element form of bindingKey. Identifies the bindingKey value associated with a bindingTemplate. Primary Data type: Describes an instance of a web service in technical terms. Service element. Collection accessor for bindingTemplate information. Primary Data type: Describes an instance of a business or business unit. Data: This structure is the container for safely extending the businessEntity information in private implementations of UDDI compatible registries. Official operator nodes may not provide extended data but must return a properly populated businessEntity structure within this structure in response to a get_businessDetailExt message. to support customization/extensibility Data - This element is used as a short form of the BusinessEntityelement as a first pass result set for "find businesses" queries. Accessor container for one or more businessInfo structures This is the element form of businessKey. Identifies the businessKey value associated with a businessEntity. Primary Data type: Describes a logical service type in business terms. Service element. Accessor collection point for businessService data. Service element. Used in searching and categorization. This is the element form of the completionStatus attribute. Data: a contact Service element: accessor for one or more contacts. A textual, short description. When adorned with an xml:lang markup, signifies a description in a specific language. Data: A url pointing to an external (typed by convention) discovery doc. Service Element: accessor for one or more discoveryURL elements Data: an email address. Supports the DispositionReport structure. Provided for conveying text and structured error code (alphanumeric) information. Error message text is contained by this element. Returned on output. Signifies error status in a dispositionReport. See error code appendix in the API specification. This element modifies the behavior of the find operations. See the search qualifiers appendix in the UDDI API specification. Service Element: container/accessor for findQualifiers This is a place holder for a businessKey value. It is used in several messages and is not intended to always represent a positional place in a relationship. Data: present only when the service is provisioned via remote hosting,load balancing, etc. Mutually exclusive with accessPoint. Service element. Used in searching and categorization. Support element: used to contain optional information about the way an instance of a web service is implemented or varies from the general specifications outlined in a specific tModel. An individual binding property. This is a general purpose field for use in providing more specific information associated with a tModel fingerprint component within a bindingTemplate. Depending on the meaning or concept represented by the tModel reference (depends on the tModel creator's intent), this element will hold data meaningful to those who understand it's purpose based on that intent. This is the element form of keyValue. See the attribute form description for more information. Represents a namespace qualified name-value pair. Depending on use context, this structure can be used within different convention frameworks. V2 CHANGE: On playback, a record saved without a keyName attribute is returned without the attribute as well. The behavior of saving without a tModelKey is promotion to the keyword namespace by operator assignment of the keyedReference to the uddi-org:general namespace. Used to report which keys involved with an assertion are managed by the publisher who is viewing the data. This is a support element that is part of the assertionStatusReport A textual representation of a name. When used with tModel, suggested format is URN. With other entities, more than one name may be supplied, as long as each name is adorned with a unique xml:lang value to signify the language that the name is expressed in. Support element - used to contain an on-line description and a URL pointer to more in-depth or external documentation. A uniform resource locator (URL) that can be used to get more information or specifications The name associated with a contact. Blank if no name applies. For transliteration purposes (e.g. romanization) the suggested approach is to file multiple contacts. Data: an telephone number. This is used in the set_publisherAssertions message to specify a relationship assertion. See set_publisherAssertions before using this element. Data - used in response to get_relatedBusinesses. This element is used to give brief information about a related business and the shared relationships. Used to convey the relatedBusiness information for a particular businessEntity. Service Element: This structure supports the dispositionReport structure. Used to signify the type of key associated with the result report. Returned on output. The numeric equivalent of the errCode value. 0 signifies success. This structure is used as the short form of a service for list purposes. V2 CHANGE: multiple names allowed for internationalization support. Accessor container for one or more serviceInfo structures The element form of the serviceKey attribute. This is a collection of relationship information. This structure defines a metadata about a technology, specificationor namespace qualified list (e.g. taxonomy, organizaton, etc.) Support element used in searches by tModel key values Data: This structure is used to enumerate short form tModel information. Support element - accessor container for tModelInfo. Support element used as a container for tModel "fingerprint" within a web service bindingTemplate metadata set. Support element: used to contain implementation instance specific information about compatible specications (via tModel reference) and optional settings details. Think of these as binding properties. The element form of the tModelKey attribute. This is a place holder for a businessKey value. It is used in several messages and is not intended to always represent a positional place in a relationship. A uniform resource locator (URL). Defined for historical purposes. Not supported in UDDI V1 and V2 operator registries. May be used by private registries to specifiy location of data to be imported into a registry instance. Message - Request: This message is used to add new assertions to the existing set of assertions tracked on a per-publisher basis. Message - Response: This message is a response to the get_assertionStatusReport message. It is a report of all complete and incomplete assertions and serves an administrative use involving determinine if there are any outstanding, incomplete assertions about relationships involving businesses the publisher account is associated with. Message - Response: used to return an authentication token in response to a "get_authToken" message. Message - Response: Returns one or more bindingTemplate structures based on the input passed. This is the response to a get_bindingDetail message. Response to get_bindingDetail and save_binding messages. Message - Response: Returns one or more businessEntity structures. This is the natural response to a get_businessDetail message and to a save_business message. Message - Response: The extended businessDetail messages define an API that allows non-operator UDDI registries to provide extended information via a consistent API. This message is the response to get_businessDetailExt. Message - Response: This is a report - a list of businesses in short form. This message is the response to a find_businessEntity query. Message - Request: This message is used to delete information about a previously registered bindingTemplate structure. Message - Request: used to delete information about a previously registered businessEntity. Message - Request: This message is used to delete specific assertions to the existing set of assertions tracked on a per-publisher basis. Message - Request: used to delete information about a previously registered businessService structure. Message - Request: used to Hide information about a previously registered tModel. Message - Request: used to deactivate an authentication token that was obtained by a call to get_authToken. Message - Response: This message is used report the outcome of calls. It is used within error (fault) messages, and can stand alone when indicating success. Message - Request: This message is used to search for summary results listing registered bindingTemplate data within a businessService matching specific criteria. Message - Request: This message is used to search for summary results listing registered businessEntity data matching specific criteria. V2 CHANGE: allows up to 5 xml:lang qualified names One of the arguments name, identifierBag, categoryBag, tModelBag or discoveryURLs must be supplied for data to be returned. Message - Request: This inquiry API message is used to get information about businessEntity data that are related to a particular businessEntity in a particular way. Only those relationships whose assertion status is complete are reported. No data is reported in the response to this request unless the publisher of that businessEntity and the publisher of the businessEntity key passed in the inquiry have made relationship assertionst that agree. Message - Request: This message is used to search for summary results listing registered businessService data matching specific criteria. V2 CHANGE: allows up to 5 xml:lang qualified names One of the arguments name, identifierBag, categoryBag or tModelBag must be supplied for data to be returned. Message - Request: used to search for summary results listing registered tModel data matching specific criteria. One of the arguments name, identifierBag, or categoryBag must be supplied for data to be returned. Message - Request: This message is used to request the current status of relationship and reference information based on the relationship data defined in the publisherAssertions message. Message - Request: used to request an authentication token. The response is an authToken message. Part of a user credential. Used with get_authToken message. User credentials. Typically a password. Can be a certificate or signed piece of data as well. Message - Request: Used to get one or more bindingTemplate structures back based on the identifiers passed. Response is bindingDetail Message - Request: This message is used to get the detailed information registered about businessEntity data matching specific key value(s). Message - Request: The extended businessDetail messages define an API that allows non-operator UDDI registries to provide extended information via a consistent API. This message is the request that will cause a businessDetailExt message to be returned. Message - Request: This message is used to get the complete set of assertion information managed by a particular publisher. The response is a publisherAssertions message that contains the full assertion set for the publisher associated with the authInfo token.. Message - Request: This message is used to support tool resynch by allowing a query to get summarized information about registered businessEntity and tModels for a given userID. This API is intended to let publishers determine what they've published. As such, authentication is required. The response is a registeredInfo message. Message - Request: This message is used to get the detailed information registered about businessService data matching specific key value(s). Message - Request: used to request the details about one or more specific tModel structures. Results are returned in a tModelDetail message. Message - Response: response to get_publisherAssertions request and the set_publisherAssertions message. Contains all of the relationship assertions made by the requesting publisher. This one structure contains all of the relationships recorded by the publisher. Message - Response This structure is used in the resynch process and is a response to a get_registeredInfo message. Message - Response: This is a report - a list of related businesses in short form. This message is the response to a find_relatedBusinesses query. Message - Request: This message is used to save (add/update) information about one or more bindingTemplate structures. Message - Request: used to save (add/update) information describing one or more businessEntity structures. One of businessEntity or uploadRegister is required. Invalid if contains both or neither type. Message - Request: used to save (add/update) information about one or more businessService structures. Message - Request: used to register or update a tModel. One of tModel or uploadRegister is required. Invalid if contains both or neither type. Message - Response: This message is used to return full businessService details. Message - Response: This message is used to return results of a find_service request. Message - Request: This message is used to save all relationship assertions information managed by a particular publisher. The response is a publisherAssertions message containing all of the currently registered assertions for an individual publisher account. Message - Response: returns all exposed details about a tModel. This is the response to a get_tModelDetail message. Message - Response: This is a report - a list of tModels in short form. This message is the response to a find_tModel query. This defines the SOAP 1.1 body that will be used by operators who call third party validation services.