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
[email protected]
+1 703-518-4174
At 10:16 PM 8/17/00 -0400, David RR Webber wrote:
>Message text written by INTERNET:[email protected]
> >|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.
