[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [uddi-spec] The New Draft of the TN: "UDDI as the registry for ebXML components"
Joel, I am proceeding on a couple of tracks with ebXML. I have attempted to go directly to the CPPA and Messaging TCs to review the portions of the TN that involve aspects of their specifications. On Wednesday I got an indication from the Chair of CPPA that he is willing to make an effort to have either himself or a member of his TC to look over the TN. he's been sent the latest version and we should hopefully get feedback from that TC soon. I'm having a harder time getting a hold of the Messaging TC, but will keep trying. Another track is to bring the idea of an ebXML community managed taxonomy to the Joint Committee for ebXML. This will take more time than I believe the TN should wait, but would be worth while in the long run. Regards, Paul Macias -----Original Message----- From: Luc Clement [mailto:email@example.com] Sent: Thursday, March 20, 2003 12:51 AM To: firstname.lastname@example.org Cc: Munter, Joel D Subject: FW: [uddi-spec] The New Draft of the TN: "UDDI as the registry for ebXML components" Posted on behalf of Joel Munter -----Original Message----- From: Munter, Joel D [mailto:email@example.com] Sent: Wednesday, March 19, 2003 21:43 To: Luc Clement Subject: FW: [uddi-spec] The New Draft of the TN: "UDDI as the registry for ebXML components" I was blocked from posting this reply. Would you please? Joel Munter, Intel desk: 480.552.3076 cell: 602.790.0924 -----Original Message----- From: Munter, Joel D Sent: Wednesday, March 19, 2003 10:25 PM To: 'Keisuke Kibakura'; UDDI Spec. TC Subject: RE: [uddi-spec] The New Draft of the TN: "UDDI as the registry for ebXML components" Kibakura-san, In a recent brief exchange on the ebXML list, initiated by Paul Macias, Paul and I repeatedly asked folks on the ebXML list to take up your simple challenge to review your paper. If anyone else would like to add to this reply, please do. In discussion, they made much more of the effort than is necessary and after a series of wildly diverging replies, I am unsure of where the request to review the draft is. It is my recollection that they talked about taking the "issues" to a Joint committee. I do not know if and when anyone from the ebXML RegRep list will take the time to do the simple review requested. As you are just as aware of ebXML as you are UDDI, if I were you, I would not wait for them to do this. You might be waiting awhile. Do the best that you can without their review. Joel Munter, Intel desk: 480.552.3076 cell: 602.790.0924 -----Original Message----- From: Keisuke Kibakura [mailto:firstname.lastname@example.org] Sent: Wednesday, March 19, 2003 6:52 PM To: UDDI Spec. TC Subject: [uddi-spec] The New Draft of the TN: "UDDI as the registry for ebXML components" All, The latest draft of the TN: "UDDI as the registry for ebXML components"is now posted to the OASIS web site. It was reviewed by the editors (Luc, Daniel, and Tony, thanks!). Though it doesn't have a big change compared to the previous version, it includes many improvements. They are in the draft folder on the OASIS site: http://oasis-open.org/committees/uddi-spec/doc/draft/ Note: Since the sub-committee has not resolved some issues yet which needs the feedback from the ebXML community, the documents are not linked from the official UDDI TC page. You can find a the document at the following location. the HTML version: http://oasis-open.org/committees/uddi-spec/doc/draft/uddi-spec-tc-tn-udd i-ebxml-20030319.htm and the PDF version: http://oasis-open.org/committees/uddi-spec/doc/draft/uddi-spec-tc-tn-udd i-ebxml-20030319.pdf The HTML version of the Open Issues List: http://oasis-open.org/committees/uddi-spec/doc/draft/uddi-spec-tc-tn-udd i-ebxml-Open-Issues.htm I'd like everyone to review them above, and send comments if you have. The sub-committee is trying to obtain the feedback we need from the ebXML community. The action is led by Paul Macias (thanks, Paul). AR019 is completed. Regards, Keisuke Kibakura