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

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-dev message

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


Subject: RE: [uddi-dev] ebXML registry and UDDI comparisons


Oops... hit return and found that nasty little Outlook bug that sends the
message out when you least expect it.... more below.

-----Original Message-----
From: Luc Clement [mailto:luc.clement@systinet.com] 
Sent: Thursday, June 23, 2005 21:16
To: 'Farrukh Najmi'
Cc: 'Governor James'; 'Jørgen Thyme'; 'uddi-dev@lists.oasis-open.org'
Subject: RE: [uddi-dev] ebXML registry and UDDI comparisons



-----Original Message-----
From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM] 
Sent: Thursday, June 23, 2005 13:56
To: Luc Clement
Cc: 'Governor James'; 'Jørgen Thyme'; uddi-dev@lists.oasis-open.org
Subject: Re: [uddi-dev] ebXML registry and UDDI comparisons

Luc Clement wrote:

> “likely to follow” is entirely speculative on your part. Let me be 
> equally speculative: “no others will”.
>
“likely to follow” is speculative which is a fine thing to so.

“no others will” is an assertion with no facts to back it up. Sounds
like an emotional "knee-jerk" reaction to me (speculative statement) ;-)

[<lc> eh... neither statement can be substantiated - that was the point.
</lc>] 

That standard coexist, is an undeniable fact of life, one that is driven 
by the daily realities that  user communities have to content with given the
lack of collaboration
to avoid overlapping standards.

[<lc> Cute. ... That said, there was a recognition of the need to support
ebXML to address the needs of activities such as described by Patrick Chan
earlier today: "I am currently at the Asia ebXML EAC meeting in Hong Kong.
We have seen quite a number of case studies in Asia revolving on work that
utilises ebXML (e.g. DTTN (Digital Transportation and Trading Network) in
Hong Kong that leverages ebMS but not the registry at the moment, e-Taiwan
project, Sony Music in Hong Kong etc.)."

That was one of the motivations for example for releasing the ebXML/UDDI [1]
mapping. When these projects identify a need for registry (not surprising
they haven't to date given the field of application) they will have options.

I'm check'in out of this thread - not sure what and who's cause it serves.

[1]
http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-uddi-e
bxml.htm

</lc>] 

> * From: * Governor James [mailto:jgovernor@redmonk.com]
> *Sent:* Wednesday, June 22, 2005 10:03
> *To:* Jørgen Thyme; uddi-dev@lists.oasis-open.org
> *Subject:* RE: [uddi-dev] ebXML registry and UDDI comparisons
>
> Sun already supports a dual registry strategy, as does infravio. 
> Others are likely to follow, WS-I fud notwithstanding.
>
> Coexistence is surely the best approach.
>
> * From: * Jørgen Thyme [mailto:jt@globeteam.com]
> *Sent:* 22 June 2005 13:54
> *To:* uddi-dev@lists.oasis-open.org
> *Subject:* [uddi-dev] ebXML registry and UDDI comparisons
>
> I have looked at the specs for v3 for the ebXML registry. Although the 
> information model looks more detailed than in UDDI my immediate 
> thinking was that adding my taxonomies in UDDI I can achieve a lot. 
> And there are several implementations of UDDI.
>
> What are your thoughts? Will vendors of UDDI registries add ebXML 
> registry functionality to their existing products? Or will there be a 
> complete new set of registry products coming?
>
> Best regards / Med venlig hilsen
>
> Jørgen Thyme
>
> Development Team
> Globeteam A/S
> Gentoftegade 118-120
> DK-2820 Gentofte
>
>
> Tlf.: +45 70 26 29 70
> Fax.: +45 70 26 29 80
>
> Mobil: +45 40 90 41 67
>
> jt@globeteam.com <mailto:jt@globeteam.com>
>


-- 
Regards,
Farrukh Najmi

Coming to Java ONE 2005? If so check out Sun's Service Registry at Booth
#802 in the Java ONE Pavillion.

Sun's Service Registry Web Site:
http://www.sun.com/products/soa/registry/

Press Release:
http://www.sun.com/smi/Press/sunflash/2005-06/sunflash.20050615.1.html




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