[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ebXML TN tModels
Here are the 'common' tModels that are defined in UDDI As the Registry for ebXML Components TN.
ebXML Specification Taxonomy tModel
tModel Name:
ebxml-org:specifications
tModel Description:
ebXML Specifications Taxonomy
tModel UDDI Key (V3):
uddi:ebxml.org:specifications
Derived V1, V2 format Key:
uuid:da52cf72-2cb2-39a9-ad1e-577e66d8a6f6
Categorization:
categorization
Checked:
No
The following values are defined for this ebXML Specifications taxonomy:
ebXML:CPPA
ebXML Collaboration Protocol Profile and Agreement
ebXML:MS ebXML
Message Service
ebXML:BPSS
UN/CEFACT - ebXML Business Process Specification Schema
ebXML
Message Service v1.0 tModel
tModel Name:
ebxml-org:MessageService:v1_0
tModel Description:
ebXML Message Service v1.0
tModel UDDI Key (V3):
uddi:ebxml.org:messageservice:v1.0
Derived V1, V2 format Key:
uuid:c8692873-1842-3b32-b980-8fa6d16676d2
Categorization:
specification
ebXML
Message Service v2.0 tModel
tModel Name:
ebxml-org:MessageService:v2_0
tModel Description:
ebXML Message Service v2.0
tModel UDDI Key (V3):
uddi:ebxml.org:messageservice:v2.0
Derived V1, V2 format Key:
uuid:9a3b93be-515e-34c7-90c7-b05cdfdba8c3
Categorization:
specification
ebXML CPP
v1.0 tModel
tModel Name:
ebxml-org:CollaborationProtocolProfile:v1_0
tModel Description:
ebXML Collaboration Protocol Profile
v1.0
tModel UDDI Key (V3):
uddi:ebxml.org:collaborationprotocolprofile:v1.0
Derived V1, V2 format Key:
uuid:e3f3df4f-b221-33b4-a3ff-17b21410c565
Categorization:
specification
ebXML CPP
v2.0 tModel
tModel Name:
ebxml-org:CollaborationProtocolProfile:v2_0
tModel Description:
ebXML Collaboration Protocol Profile
v2.0
tModel UDDI Key (V3):
uddi:ebxml.org:collaborationprotocolprofile:v2.0
Derived V1, V2 format Key:
uuid:43ed4af4-eacf-3b20-95d1-c7c197f5d9d0
Categorization:
specification
ebXML CPA
v1.0 Template tModel
tModel Name:
ebxml-org:CollaborationProtocolAgreement:v1_0:Template
tModel Description:
ebXML Collaboration Protocol Agreement v1.0
Template
tModel UDDI Key (V3):
uddi:ebxml.org:collaborationprotocolagreement:v1.0:template
Derived V1, V2 format Key:
uuid:5ab4e3af-2e67-3a4f-b9b7-92a436be8f43
Categorization:
xmlSpec
ebXML CPA
v2.0 Template tModel
tModel Name:
ebxml-org:CollaborationProtocolAgreement:v2_0:Template
tModel Description:
ebXML Collaboration Protocol Agreement v2.0
Template
tModel UDDI Key (V3):
uddi:ebxml.org:collaborationprotocolagreement:v2.0:template
Derived V1, V2 format Key:
uuid:86c6fcb3-8c73-33a7-8635-38438b76aee7
Categorization:
xmlSpec
UN/CEFACT
- ebXML Business Process Specification
Schema v1.10 tModel
tModel Name:
untmg-org:BusinessProcessSpecificationSchema:v1_10
tModel Description:
UN/CEFACT - ebXML Business Process Specification Schema
v1.10
tModel UDDI Key (V3):
uddi:untmg.org:businessprocessspecificationschema:v1.10
Derived V1, V2 format Key:
uuid:1a2a88af-54f8-316c-aaf1-e1fc2ef1c0e9
Categorization: specification
-----Original Message-----
From: Luc Clement [mailto:lclement@windows.microsoft.com]
Sent: Wednesday, September 24, 2003 7:02 AM
To: uddi-sc@lists.oasis-open.org
Cc: uddi-spec@lists.oasis-open.org
Subject: FW: [uddi-spec] Use of UDDI.org as a means of promoting TC, UBR, Std Group and Consortium tModels and Value SetsDear Steering Committee members,The UDDI Spec TC would like to request the addition of a page on the uddi.org member section's web site. I've included by way of introduction some background below. In short, the UDDI community, standards groups, the TC, and consortia in particular, need a forum for advertising and registering the existence of value set and Web service interface tModels. We feel that this is a very important and valuable means of promoting UDDI and rallying community support.Please find attached a prototype of the page we would like posted. The process suggested on the page calls for organizations to make a request to the SC. The TC undertakes to provide you support in assessing the request and making a recommendation as to whether sufficient information is available to post the registration or make recommendations that would allow you to do so (once satisfied).We hope you will support this request and proceed to its implementation at the earliest possible opportunity.Thanks in advance,Luc Clément
Microsoft
Co-chair, OASIS UDDI Spec TC
From: Luc Clement [mailto:lclement@windows.microsoft.com]
Sent: Monday, September 22, 2003 13:49
To: uddi-spec@lists.oasis-open.org
Subject: RE: [uddi-spec] Use of UDDI.org as a means of promoting TC, UBR, Std Group and Consortium tModels and Value SetsMany will recall this mail and the ensuing discussion. I took an AR to make to update the prototype proposed and would like to offer this update to the TC for re-consideration.I would like to add this topic as a new agenda item. Please review either of the Word or HTML versions of the document and offer your comments. If the TC will agree with the prototype and the approach, I would like us to request comments from the Steering Committee and an update to the UDDI.org Member Section web site.Luc Clément
Microsoft
Co-chair, OASIS UDDI Spec TC
From: Luc Clement [mailto:lclement@windows.microsoft.com]
Sent: Tuesday, May 13, 2003 17:45
To: uddi-spec@lists.oasis-open.org
Subject: [uddi-spec] Use of UDDI.org as a means of promoting TC, UBR, Std Group and Consortium tModels and Value Sets(Apologies for my last and premature mail)A few meetings ago, the topic of where to post non-normative tModels came up in a discussion; we never concluded this discussion. I'd like to revive it and obtain your input on the following.BackgroundAs some of you may know, during the course of the v3 spec development, we removed from the spec those tModels and value sets that were not considered appropriate to make normative in favour of having the UDDI Business Registry (UBR) to manage these. They include the following:1 UDDI Business Registry Value Set tModels: Category System, Identifier Systems and Categorization Groups1.1 North American Industry Classification System (NAICS) 1997 Release
1.2 United Nations Standard Products and Services Code System (UNSPSC) Version 7.3
1.3 ISO 3166 Geographic Code System
1.4 ISO 3166 Code Derivation for Business Locations
1.5 ISO 3166 and UNSPSC Code Group System
1.6 World Geodetic System 1984
1.7 WGS 84 Latitude Code System
1.8 WGS 84 Longitude Code System
1.9 WGS 84 Altitude Code System
1.10 Geographic Precision Code System
1.11 UDDI Business Registry Postal Address Structure
1.12 Dun & Bradstreet D-U-N-S® Number Identifier System
1.13 Thomas Register Supplier Identifier Code System
1.14 ISO 6523 International Code Designator (ICD) System2 UDDI Business Registry Core tModels2.1 Domain Key Generator for the UDDI Business Registry Domain
2.2 UDDI JIS X 4061 Japanese sortOrder qualifierThe UBR's Operator's Council is currently in the process of reviewing these tModels in support of its UDDI v3 deployment work. This topic is long overdue.TC, Standards Groups and Consortium NeedsAs we've discussed and continue to encounter, the TC, other standards groups and consortium need a place where they can collect and promulgate the existence of their tModels and value sets (e.g. WSDL v2 TN, ebXML TN, etc).ProposalThe UBR Operator's Council is considering asking the UDDI Steering Committee to post UBR tModels on UDDI.org. At the same time, the OC discussed the need/desire for the TC/Consortium to have a similar forum and thought that we should consult the TC.To this end, the OC has created a prototype page to be added to the UDDI.org site; please find it attached. The prototype suggests the addition of a "Common tModels" navigation link which displays the content of the attached.Please review this prototype. This matter will be put on the agenda for the next TC call.Action RequiredA. The OC is soliciting your support and interest for this; while it can proceed independently from the TC, it would be best to coordinate this.B. We need to discuss the criteria for what gets published on the page; I would expect the Steering Committee to be the gate keeper but they would require guidance from the TC on matter of criteriaAs a next step once we complete this discussion and if the TC is favourable to posting such information, the next step would be for the TC (and the OC) to make a request to the UDDI-SC asking for this content to be posted.For your consideration.LucLuc Clément
Microsoft
Co-chair, OASIS UDDI Spec TC
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]