RE: [uddi-spec] Draft TN: "UDDI as the registry for ebXML compone nts"

["Von Riegen, Claus" <claus.von.riegen@sap.com>]

Keisuke,

You have a done a good job in writing up the TN. Especially, I like the way how you base the examples on the scenario you outline in section 2.2.1.

Here are several suggestions that might improve the TN's usability:

1) UDDI Version
I support Max' idea that the TN should cover both UDDI Version 2 and 3, since no major change should be necessary for V3.

2) ebXML Specification Taxonomy tModel (Section 2.2.2)
Similar to the UDDI Types Taxonomy, the concrete categories should be linked in a hierarchical manner to the generic "ebXML" value. Also, I don't see a need for the "ebXML:TA" value. What would it represent?

3) ebXML Message Service tModel (Section 2.2.3)
The first two categories are necessary, but the third one ("ebXML:MS") doesn't seem to be appropriate, since the ebXML Message Service tModel represents the protocol, and thus is not a Web service type that is based on ebXML Mesaaging Service.

Claus 

-----Original Message-----
From: Keisuke Kibakura [mailto:kibakura@jp.fujitsu.com] 
Sent: Donnerstag, 9. Januar 2003 18:38
To: uddi-spec@lists.oasis-open.org
Subject: [uddi-spec] Draft TN: "UDDI as the registry for ebXML components"


All,

Please find attached my initial version of the TN "UDDI as the 
registry for ebXML components".

I have to apologize that it is out so late and consumed your review
time before today's telecon. 

Plaese review and send comments to the list or me. 
Any comments are welcome!

Regards, 

--
Keisuke Kibakura