[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Positioning with UDDI (was RE: Tactical Proposal: Split V2 wo rkitems into V2 and V3 (repost))
reply: What I intended by my statements (it seems like a long time ago now) is precisely what Scott just restated. I clearly understand that most of the current Oasis Registry TC specifications and Information model is "registry" based, leaving the details of the repository to implementations. My goal with my original statements was to identify the need to kick-off an Interoperability sub-team within the Oasis Registry TC to evaluate and bring to light the best alternatives for bridging the gap between the Oasis registry TC and UDDI. If the study of alternatives leads that way, that team would also have within its scope the responsibility for drafting any artifacts such as relevant Service Types (aka tModels) to support the registration of ebXML Registries within UDDI and so on. Joel -----Original Message----- From: Scott Hinkelman [mailto:srh@us.ibm.com] Sent: Wednesday, August 22, 2001 7:12 AM To: regrep@lists.oasis-open.org Subject: Re: Positioning with UDDI (was RE: Tactical Proposal: Split V2 wo rk items into V2 and V3 (repost)) I believe that Joel M's suggestion on potentially utilizing UDDI as the Registry function has merit. At the same time, clearly there are issues with this potential including alignment with a Project vrs an Open Standard body as David W. outlines, the issues of the ebXML output spec being more focused on registry as Farrukh outlines (which is not mandated to be such for an OASIS effort I would believe, especially in light of any coordination efforts that can be established), and what is currently in scope for the OASIS group concerning tModels as Lisa outlines. However, given the current timing of emerging UDDI V3 formulation and OASIS in between ebXML Exit and the first TC Specification since then, the opportunity to define a clear RegRep eBusiness environment across efforts has not been better. I believe Joel M. suggested a task force/ sub-group to address this issue. Speaking for myself and IBM, I support Joel M. in this suggestion, and know IBM will make efforts to support this. We do not want overlap or confusion in the RegRep eBusiness space and see value in both efforts. Scott Hinkelman, Senior Software Engineer XML Industry Enablement IBM e-business Standards Strategy 512-823-8097 (TL 793-8097) (Cell: 512-940-0519) srh@us.ibm.com, Fax: 512-838-1074 ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC