|
|
|||||||||
|
|
|
|
|
|
|
|
|
|
  About Join Governance Members Contact Us  Forums White papers Case Studies Technical Info Solutions Common tModels FAQs  IPR Policy TC Guidelines  Current TC List UDDI Spec  OASIS CGM Open DCML LegalXML PKI   CoverPages XML.org Sponsorship |
Show me currently published tModels 
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 you can publish these tModels in a UDDI registry such as the UDDI Business Registry (UBR), promulgating their existence is also important. The OASIS UDDI Member Section wants to encourage and promulgate common tModels promoted by standards groups and consortiums. 
The registration of tModels with the Member Section 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 Register page of the Member Section. Technically, the tModel should follow basic recommendations and best practices for UDDI registrations. Therefore, it must contain:
It should also:
The request to register your tModel with the Member Section the OASIS UDDI Member Section public mailing list at uddi-ms-comment@lists.oasis-open.org. In order to be considered, the tModel needs to have been published in the UBR and the request must include the following information:
The OASIS UDDI Member Section, with the aid of the OASIS UDDI Specification TC, will validate the request against above criteria and, once accepted, will post the tModel information to this page. 
1 Categorization and Identifier System tModels
2.1 ebXML Specification tModels
2.2 update_entities Web service
2.3.1 WSRP Service Type tModel 2.3.2 WSRP v1 Bindings tModel 2.3.3 WSRP Producer Service Reference tModel 2.3.4 WSRP Portlet Handle tModel 2.3.5 WSRP v1 ServiceDescription PortType tModel 2.3.6 WSRP v1 Markup PortType tModel 2.3.7 WSRP v1 Registration PortType tModel 2.3.8 WSRP v1 PortletManagement PortType tModel 2.3.9 WSRP v1 ServiceDescription SOAP Binding tModel 2.3.10 WSRP v1 Markup SOAP Binding tModel 2.3.11 WSRP v1 Registration SOAP Binding tModel 2.3.12 WSRP v1 PortletManagement SOAP Binding tModel 1 Categorization and Identifier System tModels1.1 ebXML Specification Taxonomy tModel
1.2 Protocol Categorization
1.3 Transport Categorization
1.4 WSDL Entity Type tModel
1.5 WSDL portType Reference tModel
1.6 WS-I Profile Conformance Claim tModel
1.7 XML Namespace tModel
1.8 XML Local Name tModel
2 Specification tModels2.1 ebXML Specification tModels2.1.1 UN/CEFACT - ebXML Business Process Specification Schema v1.10 tModel
2.1.2 OASIS ebXML CPA v1.0 Template tModel
2.1.3 OASIS ebXML CPA v2.0 Template tModel
2.1.4 OASIS ebXML CPP v1.0 tModel
2.1.5 OASIS ebXML CPP v2.0 tModel
2.1.6 OASIS ebXML Message Service v1.0 tModel
2.1.7 OASIS ebXML Message Service v2.0 tModel
2.2 update_entities Web service2.2.1 update_entities Web service for UDDI Version 2 entities
2.2.2 update_entities Web service for UDDI Version 3 entities
2.3 WSRP Canonical tModels2.3.1 WSRP Service Type tModel
2.3.2 WSRP v1 Bindings tModel
2.3.3 WSRP Producer Service Reference tModel
2.3.4 WSRP Portlet Handle tModel
2.3.5 WSRP v1 ServiceDescription PortType tModel
2.3.6 WSRP v1 Markup PortType tModel
2.3.7 WSRP v1 Registration PortType tModel
2.3.8 WSRP v1 PortletManagement PortType tModel
2.3.9 WSRP v1 ServiceDescription SOAP Binding tModel
2.3.10 WSRP v1 Markup SOAP Binding tModel
2.3.11 WSRP v1 Registration SOAP Binding tModel
2.3.12 WSRP v1 PortletManagement SOAP Binding tModel
3 Protocol tModels3.1 HTTP Protocol tModel
3.2 SOAP Protocol tModel
4 Metadata tModels4.1 WSDL Address tModel
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||