OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-jc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: FW: Assistance please - FW: ebXML TC review and input of the UDDI Spec TC "UDDI as the registry for ebXML components"

Dale and JC,
I found this e-mail from Luc this morning as I was catching up on my e-mail. It looks like it may not have been sent to the entire JC. 
It appears to me that this e-mail contains a lot of the information we needed for clarification on the request from Luc.  Near the bottom of the e-mail he provided examples of how they would like to use URLs, keys, and namespaces.  Does this answer our questions on what they need from us?  I hesitate to send a note to Luc asking for clarification, when he thought he had already sent this to us. 
I suggest we all review this and discuss on e-mail to see if this answers our questions. Perhaps we need another short telecon this week to discuss his requests, and provide some answers.
Please let me know if we need additional clarification from Luc and I will be happy to follow-up with a note to him. 
OASIS ebXML Registry TC Chair
-----Original Message-----
From: Luc Clement [mailto:lclement@windows.microsoft.com]
Sent: Friday, July 04, 2003 2:57 PM
To: James (Jamie) Bryce Clark
Cc: Karl Best; jdurand@fsw.fujitsu.com; ian.c.jones@bt.com; Breininger, Kathryn R; Tom Bellwood
Subject: Assistance please - FW: ebXML TC review and input of the UDDI Spec TC "UDDI as the registry for ebXML components"

My attempts to deliver mail to cyclonecommerce.com addressees are being rejected with:

Reason: Delivery not authorized

The sender is not authorized to send to the destination.

Could you please forward this mail to Dale as I'm probably getting caught in some spam filter (I guess lclement@windows.microsoft.com must appear to be a suspicious message originator ;-) )


From: Luc Clement
Sent: Friday, July 04, 2003 14:35
To: 'dmoberg@cyclonecommerce.com'
Cc: 'jdurand@fsw.fujitsu.com'; 'ian.c.jones@bt.com'; 'thryn.r.Breininger@boeing.com'; 'Tom Bellwood'; Karl Best; James (Jamie) Bryce Clark
Subject: ebXML TC review and input of the UDDI Spec TC "UDDI as the registry for ebXML components"

To:   OASIS ebXML Joint Committee Chair, Dale Moberg dmoberg@cyclonecommerce.com


  1. OASIS ebXML Collaboration Protocol Profile and Agreement TC Chair, Dale Moberg dmoberg@cyclonecommerce.com
  2. OASIS ebXML Implementation, Interoperability and Conformance TC Chair, J Durand jdurand@fsw.fujitsu.com
  3. OASIS ebXML Messaging Services TC Chair, Ian Jones ian.c.jones@bt.com
  4. OASIS ebXML Registry TC Chair, Kathryn Breininger Kathryn.r.Breininger@boeing.com
  5. OASIS UDDI Spec TC Co-chair, Tom Bellwood bellwood@us.ibm.com
  6. OASIS: Karl Best and Jamie Clark



[1] UDDI as the registry for ebXML components, UDDI Spec TC Technical Note, http://www.oasis-open.org/committees/uddi-spec/doc/draft/uddi-spec-tc-tn-uddi-ebxml-20030508.htm 

[2] UDDI Spec TC Process, http://www.oasis-open.org/committees/uddi-spec/doc/process/uddi-spec-tc-process-20021212.htm.




I'm writing to you as Chair of the ebXML JC for the purpose of obtaining your and other ebXML TC chair's support for final review and input of the UDDI Spec TC's "UDDI as the registry for ebXML components" [1] Technical Note (TN).  As you may know, the UDDI Spec TC has approved this document as a Committee Technical Note in accordance with its TC process which you can find in Section 2 of [2].


Acting on the UDDI Spec TC's behalf, Paul Macias approached the CPPA and Messaging TCs in March of this year with a request for review and input on the portions of the TN that involve aspects of the CPPA and MS specifications referenced by the Technical Note. You agreed as Chair of the CPPA TC to present this TN to your TC for review at your TC's 27 March telecon. Paul did not get a response from the Messaging TC. Unfortunately, we did not obtain comments back resulting from this request, and thus decided to move forward for approval of the TN. I'm pleased to note though, that the ebXML RegRep TC has recently provided comment on the TN which we will consider during our 8 Jul telecon.


The TN has now been approved and ready to be posted pending finalization of names, URLs and keyspaces referring to ebXML components, and consideration of further comments we may receive as part of this activity. While the UDDI Spec TC could make such assignments and derive these from its namespace, we feel it more appropriate for these to be derived from those already defined by the ebXML community. Furthermore, we also think that these should be managed by ebXML rather than UDDI.


We ask your support in your capacity as Chair of the ebXML JC in coordinating the necessary activities allowing for the following:


a. obtain review of the TN

b. assign or confirm the appropriateness of the current assignments of the following:


·         tModel Names (e.g. ebxml-org:specifications)

·         overview document URLs used to point to ebXML specifications (e.g. http://www.ebxml.org/specs/index.htm)

·         keyspace used for UDDI v3 tModel keys (e.g. uddi:ebxml.org:specifications)


Note 1: I've provided an excerpt below to demonstrate by way of example what we are asking of ebXML TCs. I've put in yellow highlight examples of tModel names, URLs and v3 keys we seek input on.


Note 2: v1 and v2 format key derivation (by way of UDDI v3's key hashing algorithm) will be performed after we finalize the tModel keys to be assigned


If, as a conclusion of your review, you would prefer for these names and keyspaces to be assigned by the UDDI TC within its own namespace, please let Tom and I know and we will do so.


c. identify the timeframe for completion of this review


We want to finalize and post this TN as soon as possible given its approval by the TC, but will gladly delay this allowing for input from ebXML TCs.


Please let me know your thoughts at the earliest possible convenience. If it would help, I'll gladly arrange for a telecon to discuss this with you and the other chairs.


Thanks in advance for your time and consideration of this matter.

Luc Clément
Co-chair, OASIS UDDI Spec TC



Excerpt from [1]

2.2.3 ebXML Specifications Taxonomy tModel

ebXML is a framework that consists of several distinct technical specifications, each of which must be represented by tModels in a UDDI registry. UDDI tModels are usually tagged with categorizations denoting information that facilitates their discovery. That is why before defining tModels representing ebXML specifications, we define an ebXML Specifications Taxonomy tModel, which is used to categorize these tModels (described in the following section).

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:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx01 (to be derived)

Categorization:                     categorization

Checked:                               No


<tModel tModelKey="uuid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx01">


<description xml:lang="en">ebXML Specifications Taxonomy</description>








keyValue="categorization" />




keyValue="unchecked" />



The following values are defined for this ebXML Specifications taxonomy. These values are useful for classifying ebXML-related tModels and are helpful for others who want to find those tModels.

ebXML:CPPA   ebXML Collaboration Protocol Profile and Agreement

ebXML:MS       ebXML Message Service

ebXML:BPSS   ebXML Business Process Specification Schema

Please note that this tModel is a categorization system for ebXML framework specifications and does not represent ebXML specifications themselves.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]