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

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

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


Subject: Re: [uddi-spec] UTF-8/UTF-16






Hi Max,

I wanted to comment on a couple of your points.   It's obvious that there's
a real and significant impact to changing V2 in this way given that there
are a number of vendors with UDDI v2 implementations now in products.  The
return on investment for such a change should be more compelling than
anything we've heard so far.  As for v3, I think it's unlikely many
vendor's products will include serious implementations of v3 in the short
term, and thus believe the impact of making such a change to v3 is far
lower.  This doesn't change the arguement about whether it's appropriate
for us to do so.   We can also continue that topic in this list and at our
next telecon.   As far as soliciting input outside, I think that it's
appropriate that such discussion take place on the OASIS mailing lists,
rather than as a sponsored effort in other forums such as various Yahoo
Groups or elsewhere.   As for creating a web page listing the various
implementations of UDDI, there is already a place for this on uddi.org at:
http://uddi.org/solutions.html   You can get others added there by
submitting their information to the OASIS UDDI Steering Committee.

Thanks,
Tom Bellwood


Max Voskob <mvoskob@msi.com.au> on 10/16/2002 04:19:00 PM

Please respond to Max Voskob <mvoskob@msi.com.au>

To:    uddi-spec <uddi-spec@lists.oasis-open.org>
cc:
Subject:    [uddi-spec] UTF-8/UTF-16




Hi all,

I would suggest the following:

1. Drop any idea of changing v.2 unless it is  absolutely critical for
interoperability with other standards.

2. Can anyone present a strong case why  we need to change v.3?
    - question 1: Is the need to  support UTF-16 based on a solid ground
(another approved spec, candidate spec or  something like that) ?
    - question 2: Is  it beneficial to make the change regardless of any
other standard? (at the  end of the day UTF-16 is a legitimate and widely
used encoding)

3. Ask vendors to come forward and announce their  v.3 implementations so
we can estimate the impact. We can post a call on yahoo  mailing lists,
uddi-comments and probably some other popular mailing lists.

I hope this makes sense.

By the way, I would suggest to have an official  page with a list of
implementations. It will give us a clue of the scale of  impact a change
can make. I would volunteer to do this work.

Cheers,
Max
















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


Powered by eList eXpress LLC