----- Forwarded by Rimas
Rekasius/Chicago/IBM on 04/29/2005 05:25 PM -----
Rimas,
thanks for listening
My suggestions below
Bye
Thanks for your comments on the Basic
B2B Profile. I thought it was interesting that you would comment
on the name of the profile. In fact, you are not the only one to
have done so: Gartner's David Smith didn't like the name either, pointing
out that it wasn't very "basic" and that it had applicability
far beyond "B2B", and that the combination of the terms really
sells the profile short. We're considering a name change. Do
you have any specific names you'd like to suggest? Of course, changing
the name of the profile would need to be done very carefully so as not
to cause too much confusion.
I would suggest to put it in the
context of the "namespace" that ws-i is considering for its profiles.
Options
1) we want to be technical and
"reliable asynchronous" are the keywords
2) we want to be business and
call it "business critical"
3) we want to stay in the "basic"
style namespace: call it "advanced",
4) we want to be abstract and
any namespace will do: colors for example, call it the purple profile
5) use a typical application for
which this profile is the "killer": e.g. "fund transfer"
I am not sure which one I prefer
:-)
On your "when will IBM provide support" question, we obviously
can't speak for others, so you'll need to ask to them yourself, but here's
the IBM story. Our work in WS-I has convinced us that developing
a good profile requires sample applications, test tools, usage patterns,
and of course product support, in addition to the profile document; each
tends to help improve the other (usage patterns point out issues with the
profile, sample applications demonstrate how to apply the usage patterns,
etc.). So, we are considering developing some alpha/beta deliverables
to accompany this effort. What are your views regarding what sort
of content we should focus on? For instance, should we worry about
validation tools, or can we initially focus on code gen for strictly conformant
services? Also, are there patterns of Web services usage that this
profile does not cover that you think it should?
I've got a project with a customer
where I use WS6 and would like to be beta for WS7 and test drive this profile,
so my requirements in priority
order:
#1 a compliant beta WebSphere
with associated RAD tooling
#2 proof that WebSphere interoperates
with WebLogic and Windows, and less priority Axis2
#3 redbook or article explaining
the best practices for asynchronism, with sample apps...
#4 performance data
#5 validation tools can come later
I would like the profile to cover
the various asynchronous MEPs,clarifying the issues between the WSDL and
SOAP MEPs
(great article from Dave Orchard
on this topic Underlying
Protocol is a completely leaky abstraction)
I very much would like an Eventing
profile, but this belongs to a different profiel I believe
My 2 cents
--
Jacques Talbot - Teamlog 10 rue Lavoisier - 38330 Montbonnot
Tél: 04 76 61 37 12 Mél: jacques...@teamlog.com
Tél. mobile 06 07 83 42 00