[
Lists Home |
Date Index |
Thread Index
]
The telling part is the "commitment to an aggressive schedule".
My guess: they are terrified of the fragmentation over XML Schemas, the
slow pace of the W3C at this time, and the centrality of the
TAG. They have pushed a pawn to move the game along at a
pace more amenable to their product schedules.
It is the essential problem with the commercial-based
consortium: when the power players don't get what they
want, they take their ball to another field and recruit
new teams. That is predictable. They will also use
the overlapping goals of OASIS and the W3C to drive a
wedge into that relationship. Expect more reviews
of the "liaisons" and the rules for creating such.
That kicks it into committee, spreads FUD, and exhausts.
Meanwhile, a self-sustaining market emerges and the
lock-in solidifies based around a handful of workable
standards. It's called "colonization". It worked for
the W3C and has worked ever since. Game as played.
Ever wonder why the old guys used ISO? Nation/state
customers. Slow but dammed hard to derail. They
just need and should accept more programming
experts that implement independently. If ISO is
smart, they will make peace with and a home for
the open source movement. Nation states are
"of the people, by the people, for the people".
<lowblow>.. but not in Republican administrations.</lowblow>
len
-----Original Message-----
From: Simon St.Laurent [mailto:simonstl@simonstl.com]
On Thu, 2002-02-07 at 11:01, Roger L. Costello wrote:
> Yes, this is an attempt to influence how web services will be designed
> and the nature of XML messages. I am very concerned that people will
> use web services simply as another way to do tightly coupled RPC, i.e.,
> procedure name plus parameters. I think that XML-based web services
> should provide a new paradigm, where the focus is on the data and
> business processes.
Thanks very much for doing this, Roger. I'm not sure we as developers
are expected to do this kind of thinking, however, when Microsoft, IBM,
and BEA are so kind as to give us organizations for making Web Services
interoperable.
|
