RE: Positioning with UDDI (was RE: Tactical Proposal: Split V2 wo rk items into V2 and V3 (repost))

["Welsh, David" <David.Welsh@nordstrom.com>]

David ... good call 

> However - here's the rub.  The ebXML work is public domain,
> while the UDDI is not.   Therefore we have to avoid at all costs
> any situation where work is being developed within UDDI and
> then being presented to ebXML for adoption.
> 
> The best outcome would be for UDDI to create a public 
> process which we could work thru.
> 
Or those behind UDDI, saw the benefits and growing business opportunity of submitting the UDDI work to the ebXML mission. 
We'd get a common vision sooner, and the consumer would find a clearer investment picture; ie. quicker sales to developers !
Till then, it's easy for potential customers to see the same players on UDDI and ebXML competing with (hurting) themselves. Confusion typically follows and sales (associated from new business services) get delayed / slows down. In these difficult economic times, if anyone is going to wait and see
then it's going to be the new consumer; ahead of any new developers.

UDDI could be a critical mass catalyst for ebXML RegRep; and everybody wins !

Thanks
-Dave


> Thanks, DW.
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>