January 20 ebXML Requirements Conference Call

[Mike Rawlins <rawlins@metronet.com>]

Our next project team conference call will be Thursday, January 20 as
follows:

Date:    Thursday, 1/20/2000
Time:     9:30 AM - 11:00 AM PST
            10:30 AM - 12:00 AM MST
            11:30 AM - 1:00 PM CST
            12:30 PM - 2:00 PM EST
              5:30 PM - 7:00 PM GMT (London)
              6:30 PM - 8:00 PM Paris
              2:30 AM - 4:00 AM, Friday January 21, Tokyo

Phone: (334) 240-1633
Participation #: 842301

Agenda for Thursday, 1/20

1)    Roll call, introduction of new participants
2)    Approval of Agenda
3)    Approval, corrections to minutes from 1/7 and 1/13
4)    Miscellaneous updates on logistics and other activities
5)    Discuss issues list and straw poll
6)    Discuss plan for completing and reviewing a draft of the
Requirements Specification
7)    Schedule next call

The updated issues list is attached.  The minutes (in Word, text, and
HTML) from 1/7 and 1/13 may be retrieved from:

http://www.metronet.com/~rawlins/ebXML/ebxml-ReqGrp-Telcon-010700.doc
http://www.metronet.com/~rawlins/ebXML/ebxml-ReqGrp-Telcon-010700.txt
http://www.metronet.com/~rawlins/ebXML/ebxml-ReqGrp-Telcon-010700.html

http://www.metronet.com/~rawlins/ebXML/ebxml-ReqGrp-Telcon-011300.doc
http://www.metronet.com/~rawlins/ebXML/ebxml-ReqGrp-Telcon-011300.txt
http://www.metronet.com/~rawlins/ebXML/ebxml-ReqGrp-Telcon-011300.html


Mike Rawlins
ebXML Requirements Project Team Leader
--
Michael C. Rawlins, Rawlins EDI Consulting
http://www.metronet.com/~rawlins/

ebXML Requirements Issues
=========================

Last Updated 1/13/2000

1.  Conflict - Maximize interoperability with existing EDI implementations, or maximize
interoperability between ebXML applications.  

Proposed Consensus:  We should work primarily toward maximum interoperability between ebXML applications,
i.e., a single standard.   We must provide a mechanism and migration path for accomodating legacy EDI and other
XML efforts.

2.  Conflict - Maximize interoperability between ebXML applications, or maximize internationalization
by supporting multi-lingual ebXML components?  If the latter, which languages?

Consensus - Multi-lingual support has higher priority.

3.  Scope - Should the ebXML guidelines apply to business to consumer, or only business to business?

Consensus - B2B should be the primary focus and B2C secondary.  Any requirements specific to B2C are beyond our
scope.  Autmomated B2C may be within our scope, but presentation (in the sense of display to an end user) is not.

4.  Scope - Should the ebXML guidelines provide universally applicable cross industry document
definitions?

Consensus:  The guidelines should not provide these cross industry document definitions.