ebxml-core message

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


Help: OASIS Mailing Lists Help | MarkMail Help
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

Subject: VOTE REQUESTED - Suggest vote NO to Section 7 of the TechnicalArchitecture Specification

All members,

I have been examining my copy of the technical Architecture specification. I
would suggest that a vote of NO should apply to this section.

For the SME, this section is fundimentally flawed and will not work in any
Small Business that I know of.

Line 434 says "The implementation phase deals specifically with the
procedures for creating an application of the ebXML infastructure"

There is extensive descriptions following of registries, scenarios, runtime
phases etc... but there is nothing that I can find even showing how an SME
connects it to their packaged accounting system.

This is in my opinion, an extremely major flaw!

I kindof understand the benefit of using a top down methodology, but in this
case it has led to a very grave design flaw.

From the ebXML homepage, I got the impression that what was being designed
was sortof like a volkswagon. A car for the masses that businesses all over
the world could use.

The problem is that the designers so far have been concentrating so much on
a top down view of what they are designing, that they haven't bothered to
have a look at the car from the side or underneeth.

What has therefore been designed, from an implemention perspective, is much
like a car without wheels!

It just won't go!

Without connecting ebXML to the packaged accounting system so central to the
movement of every SME, what hat has been described so far, won't actually

So it doesn't matter how much you rev the ebXML engine, it will never
translate into forward motion for business. It will just sit there forever
looking like a car, sounding like a car but incapable of leaving the

I know that it's just a minor detail - but connecting the ebXML to the
Accounting system is a fairly important one I would think.

The TA document described thus far, if implemented the way it is read, would
not enable an SME to conduct business using ebXML. I just thought I'd point
that out, just a comment from somebody looking from the side.

David Lyon

----- Original Message -----
From: Paul R. Levine <plevine@telcordia.com>
To: ebXML-BP (E-mail) <ebxml-bp@lists.ebxml.org>; ebxml-ccbp-analysis
(E-mail) <ebxml-ccbp-analysis@lists.ebxml.org>;
Sent: Friday, April 27, 2001 2:36 PM
Subject: VOTE REQUESTED - Proposed Corrections to Sections 6, 7,and 8.2
ofTechnical Architecture Specification

> BP PT Members,
> We have been working the past couple of days on correcting Business
> aspects of the ebXML Technical Architecture Specification.
> This is being sent out to BP list for an informal vote on whether we
> request the TA team to submit these changes to the Executive committee.
> This
> must be done this Friday at the latest. Therefore our 'vote' will be
> following the 'white
> ballot' rule, i.e. unless you vote NO, or vote to amend, and do so by
> Friday, April 26th,
> 5:00 p.m. EDT, it is assumed that you vote YES.
> If you have any questions, please call me at (732) 699-3042.
> Regards,
> Paul Levine
> BP PT Co-lead
> (See attached file: Proposed_TA-Section-6-7-8.2_Revision.doc)

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC