ebxml-coord 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: Re: FAQ document review minutes

at the risk of running across a thread of which i only appear to be seeing part
of the dialogue, i would like to state a personal opinion (which may or may not
be shared by the QR Team).

As long as we are clear that ebXML is the "Business" end and not the 'Consumer'
end - then i would agree with you.

The technical specifications being designed by ebXML will require applications
to drive them.  As David says, when the ambiguous phrase B2C is used it is
often assumed to be some kind of web interface for the 'Consumer' end - and
ebXML is not about designing those.  As an example, the RegRep has identified
the need for Application User Interfaces and Human Interfaces - but is not
about to design the Human Interfaces (we hope!).

So i believe that whilst ebXML provides a framework into which software
providers, service providers and others will be able to plug on various
'Consumer' interfaces - it is out of scope to define these in ebXML.

To state otherwise could mislead the market into believing a Consumer will be
able to 'log on to ebXML' and do e-business.  ebXML needs to attract software
developers at the 'Consumer' end, not the 'Consumers' themselves.  We can use
this question in the FAQ to bring out that point.

Alan Kotok wrote:

> David:
> Correct:  The requirements document, paragraph 2 under Business
> Requirements, says ...
> <excerpt>
> The scope of the ebXML business requirements is to meet the needs for the
> business side of both business to business (B2B) and business to consumer
> (B2C) activities. Consumer requirements of the B2C model are beyond the
> scope of the ebXML technical specifications. Application-to-application
> (A2A) exchanges within an enterprise may also be able to use the ebXML
> technical specifications, however ebXML A2A solutions will not be developed
> at the expense of simplified B2B and B2C solutions.
> </excerpt>
> The scope therefore covers the business end of interactions with consumers.
> Has there been any discussion of ebXML Phase 2???? Best regards.
> Alan Kotok
> Director, Education and Information Resources
> Data Interchange Standards Association
> akotok@disa.org
> +1 703-518-4174
> At 10:16 PM 8/17/00 -0400, David RR Webber wrote:
> >Message text written by INTERNET:rachelf@ix.netcom.com
> > >|Why should organizations join ebXML?  If you want to get your
> >|requirements in
> >|on the development of this specification, you have to be a player.
> >|
> >|I agree with Rachel ... business-to-consumer is not out of
> >|scope.  I believe
> >|the requirements document includes exchanges with consumers.
> >|
> >|Alan Kotok<
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >
> >Alan, lets not get confused here.  The B2C restriction is to avoid
> >being dragged down into the sinkhole of Forms, stylesheets,
> >and other mechanisms EXCLUSIVE to UI stuff that even the
> >W3C has not got right yet - or should that be -especially the W3C?!.
> >
> >It is a given that B2B mechanisms we are building can also
> >support B2C - but we're not on the hook to support extended
> >B2C functions.   That's Phase 2!!!
> >
> >DW.

tim mcgrath
TEDIS   fremantle  western australia 6160
phone: +618 93352228  fax: +618 93352142

tel;cell:+61 (0)438352228
fn:tim mcgrath

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

Powered by eList eXpress LLC