|
|
UDDI Spec TC |
UDDI Version 3.0
UDDI Spec Technical Committee Specification, 19 July 2002
uddi_v3
Current version:
http://uddi.org/pubs/uddi-v3.00-published-20020719.htm
Latest version:
http://uddi.org/pubs/uddi_v3.htm
Authors:
Luc Clément, Microsoft
David Ehnebuske, IBM
Andrew Hately, IBM
Maryann Hondo, IBM
Yin Leng Husband, HP
Karsten Januszewski, Microsoft
Sam Lee, Oracle
Barbara McKee, IBM
Joel Munter, Intel
Claus von Riegen, SAP
Contributors:
Selim Aissi, Intel
Bob Atkinson, Microsoft
John Colgrave, IBM
Tom Gaskins, HP
Tom Glover, IBM
Dan Guinan, VeriSign
Christian Hansen, SAP
Thomas Hardjono, VeriSign
Richard Harrah, HP
Keisuke Kibakura, Fujitsu
Seán MacRoibeáird, Sun
Ed Mooney, Sun
Andrew Nielsen, HP
Shigeru Shimada, IBM
Christian R. Thomas, Intel
Johannes Viegener, SAP
Acknowledgements:
Sharon Boeyen, Entrust
Fennivel Chai, DealEasy
Paul Denning, MITRE
Matthew J. Dovey, Oxford University
Daniel Feygin, UnitSpace
Jeffrey Kenyon, Qwest
Anne Thomas Manes, Systinet
Takayuki Nakao, NTT Communications
Scott Wood, Cambian
Brian Young, Boeing
Abstract:
The UDDI Version 3.0 Specification describes the Web services, data structures and behaviors of all instances of a UDDI registry.
Status:
This specification has attained the status of Committee Specification. This document is updated periodically on no particular schedule.
Committee members should send comments on this Committee Specification to the uddi-spec@lists.oasis-open.org list. Others should subscribe to and send comments to the uddi-spec-comment@lists.oasis-open.org list. To subscribe, send an email message to uddi-spec-comment-request@lists.oasis-open.org with the word "subscribe" as the body of the message.
For information on whether any intellectual property claims have been disclosed that may be essential to implementing this Committee Specification, and any offers of licensing terms, please refer to the Intellectual Property Rights section of the UDDI Spec TC web page (http://www.oasis-open.org/committees/uddi-spec/).
Copyrights:
Copyright © 2001-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.
Copyright © OASIS Open 2002-2003. All Rights Reserved.
1.3 Diagrams Used in this document
1.4.1 Translations of the UDDI Specification.
1.4.2 Best Practices and Technical Notes
1.5.2 UDDI Services and API Sets
1.5.5 Affiliations of Registries
1.5.6 Person, Publisher and Owner
1.6 Representing Information within UDDI
1.6.1 Representing Businesses and Providers with “businessEntity”
1.6.2 Representing Services with “businessService”
1.6.3 Representing Web services with “bindingTemplate”
1.6.4 Technical Models (tModels)
1.6.5 Taxonomic Classification of the UDDI entities
1.8 Introduction to Internationalization
1.8.1 Multi-regional businesses
1.8.3 XML and Unicode Character Set
1.8.4 Standardized Postal Address
1.8.5 Use of Multi-languages and Multi-scripts
1.8.6 Adding Language-specific Sort Orders
1.8.7 Consistent Internationalized Search
2.3 Element and attribute types and lengths
2.3.1 Data structure, publication API, inquiry API and security API
3 UDDI Registry Data Structures
3.2.1 Keys as unique identifiers
3.2.2 Containment and references
3.7 publisherAssertion Structure
4.1.3 Support for SOAP encoding
4.1.4 Support for SOAP Headers
4.1.6 XML prefix conventions – default namespace support
4.3 Support for Unicode: Byte Order Mark
4.5 Data insertion and document order
4.5.1 Inserting Data in Entities During save_xx Operations
4.5.2 Inserting Elements in Existing Entities
4.5.3 Preservation of Document Order
4.6 XML Normalization and Canonicalization
4.7 About Access Control and the authInfo Element
4.8 Success and Error Reporting
4.8.1 dispositionReport element
4.8.2 Success reporting using the dispositionReport element
4.8.3 Error reporting using the dispositionReport element
5.1.7 Matching Rules for keyedReferences and keyedReferenceGroups
5.2.1 Publishing entities with node assigned keys
5.2.2 Publishing entities with publisher-assigned keys
5.2.3 Special considerations for validated value sets
5.2.4 Special considerations for the xml:lang attribute
5.2.9 delete_publisherAssertions
5.2.12 get_assertionStatusReport
5.2.13 get_publisherAssertions
5.2.19 set_publisherAssertions
5.4 Custody and Ownership Transfer API Set
5.4.2 Custody Transfer Considerations
5.4.7 Security Configuration for transfer_custody
5.5.1 About UDDI Subscription API functions
5.5.3 Specifying Points in Time
5.5.4 Subscription Coverage Period
5.5.5 Chunking of Returned Subscription Data.
5.5.6 Use of keyBag in Subscription
5.5.7 Subscription API functions
5.5.11 get_subscriptionResults
5.5.12 notify_subscriptionListener
5.6.1 Value Set Programming Interfaces
6.1.2 Key Generation and Maintenance
6.2 Considerations When Instantiating a Node
6.2.1 Canonical tModel Bootstrapping
6.2.2 Self-Registration of Node Business Entity
6.3 User Credential Requirements
6.3.1 Establishing User Credentials
6.3.2 Changing Entity Ownership
6.4 Checked Value Set Validation
6.4.1 Normative behavior during saves
6.5 HTTP GET Services for UDDI Data Structures
7.1 Inter-Node Policy Assertions
7.3.5 changeRecordPublisherAssertion
7.3.6 changeRecordDeleteAssertion
7.3.7 changeRecordAcknowledgment
7.3.9 changeRecordNewDataConditional
7.4.1 get_changeRecords Message
7.4.2 notify_changeRecordsAvailable Message.
7.4.4 get_highWaterMarks Message
7.5.1 Replication Configuration Structure
7.5.2 Configuration of a UDDI Node – operator element
7.5.3 Replication Communication Graph
7.6 Error Detection and Processing
7.6.1 UDDI Registry Investigation and Correction.
7.7 Validation of Replicated Data
7.8 Adding a Node to a Registry Using Replication
7.9 Removing a Node from a Registry Using Replication
8 Publishing Across Multiple Registries
8.1 Relationships between Registries
8.1.1 Root Registries and Affiliate Registries
8.1.2 A Closer Look at Inter-Registry Communication Models
8.2 Data Management Policies and Procedures Across Registries
8.2.1 Establishing a Relationship with a Root Registry
9.3.3 Policy Service within UDDI
9.4 UDDI Registry Policy Abstractions
9.4.1 Registry Policy Delegation
9.4.2 Registry General Keying Policy
9.4.3 UDDI recommended keying scheme
9.4.4 UDDI Information Access Control Policy
9.4.5 Adding nodes to a registry
9.4.6 Person, Publisher and Owner
9.4.8 Registry Authorization Policy
9.4.10 Registry Data Integrity
9.4.11 Registry Approved Certificate Authorities
9.4.12 Registry Data Confidentiality
9.4.14 Registry Privacy Policy
9.4.15 Registry Clock Synchronization Policy.
9.4.16 Registry Replication Policy
9.4.17 Support for Custody Transfer
9.4.18 Registry Subscription Policy
9.4.19 Registry Value Set Policies
9.5 UDDI Node Policy Abstractions
9.5.2 Node Publisher Generated Key Assertion
9.5.4 Node Authorization Policy
9.5.5 Node Registration and Authentication
9.5.7 Node Policy for Contesting Entries
9.5.11 Node Approved Certificate Authorities
9.5.12 Node Subscription API Assertion
9.5.15 Node discoveryURL Generation
9.6 UDDI Recommended Registry Policies
9.7.1 UDDI Registry Policy Abstractions
9.7.2 UDDI Node Policy Abstractions
10.1 Entity Key Compatibility with Earlier Versions of UDDI
10.1.1 Generating Keys From a Version 3 API Call
10.1.2 Generating Keys From a Version 2 API Call
10.1.3 Migrating Version 2 keys to a Version 3 Registry
10.1.4 Mapping v1/v2 Canonical tModel Keys to v3 Evolved Keys
10.2 Other Considerations of Version 2 Inquiry API Calls
10.2.1 keyedReferenceGroup data
10.2.3 Multiple overviewDoc data
10.2.4 Multiple personName data
10.2.5 Multiple xml:lang attributes of the same language
10.2.10 Mapping Between URLType and useType attribute on accessPoint
10.2.11 Supporting External Value Set Providers Across Versions
10.2.12 Sorting and Matching Behavior
10.3 Data Migration Considerations
10.3.1 Version 3 Schema Strictness
10.4 Considerations of Version 2 Publish API Calls
10.4.1 Data update semantics consistent with request namespace
11 Utility tModels and Conventions
11.1 Canonical Category Systems, Identifier Systems and Relationship Systems
11.1.1 UDDI Types Category System
11.1.2 General Keyword Category System
11.1.3 UDDI Nodes Category System
11.1.4 UDDI Relationships System
11.1.5 UDDI owningBusiness Category System
11.1.6 UDDI isReplacedBy Identifier System
11.1.7 UDDI validatedBy Category System
11.1.8 UDDI Derived From Category System
11.2 UDDI Registry API tModels
11.2.5 UDDI Custody and Ownership Transfer API
11.2.6 UDDI Node Custody Transfer API
11.2.7 UDDI Value Set Caching API
11.2.8 UDDI Value Set Validation API
11.2.10 UDDI Subscription Listener API
11.3 Transport and Protocol tModels
11.3.1 Secure Sockets Layer Version 3 with Server Authentication
11.3.2 Secure Sockets Layer Version 3 with Mutual Authentication
11.3.3 UDDI HTTP GET Transport
11.3.7 UDDI Telephone Transport
11.4.1 UDDI SQL99 Approximate Match findQualifier
11.4.2 UDDI Exact Match findQualifier
11.4.3 UDDI Case Insensitive Match findQualifier
11.4.4 UDDI Case Sensitive Match findQualifier
11.4.5 UDDI Diacritics Insensitive Match findQualifier
11.4.6 UDDI Diacritics Sensitive Match findQualifier
11.4.7 UDDI Binary Sort sortOrder qualifier
11.4.8 UDDI Unicode Technical Standard #10 sortOrder qualifier
11.4.9 UDDI Case Insensitive Sort findQualifier
11.4.10 UDDI Case Sensitive Sort findQualifier
11.4.11 UDDI Sort By Name Ascending findQualifier
11.4.12 UDDI Sort By Name Descending findQualifier
11.4.13 UDDI Sort By Date Ascending findQualifier
11.4.14 UDDI Sort By Date Descending findQualifier
11.4.15 UDDI And All Keys findQualifier
11.4.16 UDDI Or All Keys findQualifier
11.4.17 UDDI Or Like Keys findQualifier
11.4.18 UDDI Combine Category Bags findQualifier
11.4.19 UDDI Service Subset findQualifier
11.4.20 UDDI Binding Subset findQualifier
11.4.21 UDDI Suppress Projected Services findQualifier
11.4.22 UDDI Signature Present findQualifier
11.5.1 Domain Key Generator for the UDDI Domain
11.5.2 UDDI Hosting Redirector Specification
11.5.3 UDDI Policy Description Specification
13 Related Standards and Specifications
13.1 UDDI Specifications and documents
13.2 Standards and other Specifications
A Appendix A: Relationships and Publisher Assertions
A.2 Managing relationship visibility
B Appendix B: Using and Extending the useType Attribute
B.1.1 Using the “endPoint” value
B.1.2 Using the “wsdlDeployment” value
B.1.3 Using the “bindingTemplate” value
B.1.4 Using the “hostingRedirector” value
B.2.2 Using the “wsdlInterface” value
B.3.1 Using the “businessEntity” value
B.3.2 Using the “homepage” value
B.8 Designating a new useType value
C Appendix C: Supporting Subscribers
C.2.1 Steps for Creating a Subscription
D Appendix D: Internationalization
D.1 Multilingual descriptions, names and addresses
D.2 Multiple names in the same language
D.3 Internationalized address format