Microsoft Refuses to support ebXML

I am currently involved in a major project whose objective is to provide a
very significant industry portal for accessing web services for a partical
market sector in the UK.

Part of the process is to define the web service interface specification
that will be used. In this context, ebXML MS (v2.0c) is one of the proposals
for message 'packaging'. I have just received the latest specification which
rules out the use of ebXML MS (although I think the author is a bit confused
about what specifications he's referring to), and sites a number of grounds
for this. One of these states that :-

'Microsoft refuses to support ebXML'

The other main objection appears to be 'too complex' (can't really see why
implementing 6 SOAP headers is that hard !)

I have no particular issue with not using ebXML MS but I do have to admit to
a degree or irritation about some of the comments made including this one
(note: some of the WS-xxx specifications are also proposed, and are also
rejected mainly on the grounds of 'too early').

The proposal goes on to suggest that in the absence of anything else, where
'out of band' signals are required between consumer and provider (both
directions) these can be encoded in proprietary defined headers and in some
cases within the SOAP Body !

There are many things that I could say about this particular section of the
document but I am somewhat sensitized to the particular debate and
personalities in this project and I need to be as objective and
dis-passionate as I can be (not easy).

WS-DevCon centered on the importance of interop, a notion which I think most
of us would whole heartedly support. From a practical perspective I would
suggest (although I'm not especially comfortable with) :-

- Interop is based on standards, but perhaps more importantly [practically]
on consistent implementation of those standards within 'mainstream' tooling.

I also like keep in mind a couple of basic tenets for defining architecture
:-

- Re-invent as little as possible
- Re-use as much as possible

As I'm sure you know, Microsoft have been in and out of the ebXML work quite
a few times. There are of course political under-currents in all of the
'bodies' involved in defining standards or making proposals for
specifications. Most of us try and stay out of them, but sometimes they're
hard to ignore.

so (enough drum roll already) :-

- what IS Microsoft's position re:ebXML MS (I would welcome you own personal
opinion even if there is an official Microsoft view - is it good/bad/don't
care) ?

... and I suppose leading on from this question :-

- why was it felt that there was a need for those WS specs which overlap
(Referral - Routing - others ?)

Many thanks

Fraser.

_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*
http://join.msn.com/?page=features/virus

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.