Lists Home |
Date Index |
- From: "Dick Brooks (E)" <firstname.lastname@example.org>
- To: <email@example.com>, <firstname.lastname@example.org>
- Date: Sat, 12 Feb 2000 09:42:21 -0600
I can't speak for the ebXML repository effort but I can tell you that the
ebXML Message Routing and Transport group is examining several models
EDIINT AS2 IETF
EDIINT AS1 IETF
XML MEssaging IETF
BizTalk Biztalk.org (Microsoft)
We really are trying to determine the best solution to securely and reliably
transport XML and non-XML business documents
between parties using the Internet.
Dick Brooks (member ebXML Message Routing and Transport Group)
From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of
Sent: Friday, February 11, 2000 11:58 PM
Subject: RE: OASIS/SAX - looking around
To be honest, I am not exactly impressed with what OASIS
has accomplished so far. OASIS just seems to be not very
active in anything it does including its xml.org's schema
repository effort. This is just the opposite of W3C which
seems to do a little too much. It was luke warm on XML at
the start and now it is just too hot on XML, churning out
specs after specs, seemingly in random order and directions.
What we need are smaller standard organizations, each with
well-defined and focused charter. These organizations should
do no more than approve or disapprove standard proposals, no
matter who created them, according to the group's charter. If
the group's charter is to promote I18N, then it should review
proposals according that charter. To me, this approach would
lead to far more coherent future than the way it is now, which
is dependent on the latest visions of the powerful few.
One thing I am sure of is that, if there were such organizations,
they would have turned their thumbs down on at least one W3C
recommendations. I don't care whether the shareholders of the
standard manufacturers are well-intended. I don't care whether
my friends works on the factory floor. We need organizations that
protect the consumers from the manufacturers.
Does OASIS fit this need? I don't think so. I never heard of
OASIS opposing anything W3C or IETF did.