The UDDI Spec TC Technical Notes Process is described below.
There are several incompatible Java clients for UDDI V2 which prevents portability of UDDI applications and tools written in Java. This Technical Note aims to avoid a repetition of this for UDDI V3 by encouraging the use of a single JAX-RPC programming model for UDDI V3. This technical note describes how to generate a Java client for UDDI 3.0.2 using only the mandatory mappings from WSDL and XML Schema to Java in the JAX-RPC 1.1 Specification.
Non-ASCII characters are supported by the XML Schema anyURI datatype but are not always supported in Web service tooling.
This technical note describes the interoperability considerations when using anyURI-based data types in UDDI V3 API calls.
Taxonomies and identifier systems play an important role within UDDI. It is through categorization and identification that businesses are able to find each other and the services that meet their needs. Versions 1 and 2 of UDDI cite three common categorization schemes to encourage registrants to categorize their businesses, services and service descriptions. There are dozens of other taxonomies available that are newer, gaining in popularity, or targeted at specific constituencies. While UDDI does not mandate use of these taxonomies, it is imperative that they be made available to those who would benefit from using them.
This paper guides the providers of taxonomies and identifier systems in the registration of their taxonomies and through the process of providing a validation service. Since taxonomies and identifier systems are handled in the same way, for conciseness this paper refers to both as "taxonomies".
Providing A Value Set For Use In UDDI Version 3.
In UDDI, a value set represents a set of values that can be used to provide meaning or context to a UDDI entity. Category, identifier, and relationship type systems are all value sets. Value sets play an important role within UDDI, because it is through their use that businesses are able to find each other and the services that meet their needs.
Through the use of value sets in UDDI registries, businesses are able to find each other and the services that meet their needs. This document provides guidelines for providers of value sets on how to model, register, and validate their value sets for use in UDDI Version 3.
UDDI as the registry for ebXML Components
This UDDI Spec Technical Committee Technical Note (TN) provides technical guidance on how to use UDDI registries within the ebXML framework of B2B services. Specifically, it addresses the issues related to enabling automated discovery of ebXML framework components, such as Collaboration Protocol Profile and Business Process Specification Schema, using UDDI.
By adopting the technical guidance of this TN, users will enable trading partners and their Web services and ebXML infrastructures to interact using UDDI as a common registry.
The key partitions capability is an important UDDI v3.0 feature that provides a mechanism for publishers to assign meaningful and globally unique registry keys to entities being published. The purpose of this technical note is to explain in lay person's terms the use of key partitions for UDDI registry publishers..
BPEL4WS abstract processes describe the observable behavior of Web services. They complement abstract WSDL interfaces (port types and operations) and the UDDI model by defining dependencies between service operations in the context of a message exchange. This technical note describes the relationships between the three models and suggests how BPEL4WS abstract processes can be used in a UDDI Registry.
Using WSDL in a UDDI Registry, Version 2.0.2
The Universal Description, Discovery & Integration (UDDI) specification provides a platform-independent way of describing and discovering Web services and Web service providers. The UDDI data structures provide a framework for the description of basic service information, and an extensible mechanism to specify detailed service access information using any standard description language. Many such languages exist in specific industry domains and at different levels of the protocol stack. The Web Services Description Language (WSDL) is a general purpose XML language for describing the interface, protocol bindings, and the deployment details of network services. WSDL complements the UDDI standard by providing a uniform way of describing the abstract interface and protocol bindings of arbitrary network services. The purpose of this document is to clarify the relationship between the two and to describe a recommended approach to mapping WSDL descriptions to the UDDI data structures.
This document builds on Using WSDL in a UDDI Registry, Version 1.08, providing an expanded modeling practice that encompasses the flexibility of WSDL. The primary difference between this mapping and the one described in the existing Best Practice is that this mapping provides a methodology to represent individual Web services artifacts.
As a Technical Note, this document does not replace the Version 1 Best Practice. If the additional flexibility is not required, the existing Best Practice can still be used, particularly when the UDDI artifacts are published manually.
The current version of this Technical Note represents errata #2.
Value sets facilitate discovery of entities in UDDI registries. Value sets may consist of various types of values and hierarchies that may not always be self-explanatory, e.g. value sets consisting of codes or numbers. It is thus important that value sets be well-understood by their users and applied correctly and consistently to improve the quality of registration of entities and facilitate their discovery.
This OASIS UDDI Spec TC Technical Note provides recommendations on what Value Set Overview Documents accompanying a value set need to contain. Application of this TN will ensure consistency and completeness of Value Set Overview Documents.
Through the use of value sets in UDDI registries, businesses are able to find each other and the services that meet their needs. However, value set publishers often change their value sets by adding or deleting values and/or changing their meaning in order to meet the needs of a certain domain. This UDDI Spec TC Technical node provides guidelines to providers of value sets on how to register different versions of value sets for use in UDDI versions 2 and 3.
The UDDI Spec TC from time to time publishes Best Practices and Technical Notes. The contents of these documents are not a part of the specifications.
A Technical Note is a non-normative document accompanying the UDDI Specification that provides guidance on how to use UDDI registries. While Technical Notes represent the UDDI Spec TC's view on some UDDI-related topic, they may be prospective in nature and need not document existing practice.
A Best Practice is a non-normative document accompanying a UDDI Specification that provides guidance on how to use UDDI registries. Best Practices not only represent the UDDI Spec TC's view on some UDDI-related topic, but also represent well-established practice.
Proposal
A technical note may be written about a real implementation or application of UDDI to solve a business or technical problem, or it may be written to provide recommendations regarding interaction between UDDI and other technologies and/or standards where a widely adopted practice would benefit the Web services community.A Proposal is optional, but gives one the opportunity to present the idea for the submission to the UDDI Spec TC without the need for investing the work necessary to prepare a completed work. A proposal may take the form of a simple abstract submitted to the TC mailing list, or may even be proposed as a topic of discussion at a TC meeting. The individual making the proposal can then gauge the support present in the TC for developing the work before proceeding to the next stage.
Individuals intending to submit proposals should use the technical note template available at the following location http://www.oasis-open.org/committees/uddi-spec/doc/templates/uddi-spec-tc-tn-template.doc.
Submission
To be considered by the TC, the technical note submission must be based on a Committee Specification or OASIS Standard version of the UDDI specification. A technical note based on a future release of the UDDI specification may be created, but it will not be published until that version of the UDDI specification is released.OASIS IP rules and procedures apply for any submissions.
Technical notes must use the format of the documents available at the following location http://www.oasis-open.org/committees/uddi-spec/doc/templates/uddi-spec-tc-tn-template.doc.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4