ebXML Requirements Conference Call January 13 - Agenda

[Mike Rawlins <rawlins@metronet.com>]

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

Date:    Thursday, 1/13/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 14, Tokyo

Dial-In Number: (304) 345-7506  - Please add appropriate prefix outside
of the U.S.
Participant#: 349072

Agenda:

Agenda for Thursday, 1/13

1)    Roll call, introduction of new participants
2)    Approval of Agenda
3)    Approval, corrections to minutes from 1/7
4)    Update on ebXML steering committee call, other project teams,
logistics
5)    Discuss issues list
6)    Schedule next call

No new issues have been added to the list since our last call.  However,
we have had some good discussion on the listserv on issues #1 and #4.  I
propose we continue discussing them tomorrow.  If we can't come to a
common ground yet, I would like to see if we can articulate a majority
and a minority position for each.

The updated issues list is attached.  The minutes (in Word, text, and
HTML) from 1/7 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

I hope to have them posted on the *real* project team web page by our
next call.


Regards,
Mike Rawlins
ebXML Requirements Project Team Leader


--
Michael C. Rawlins, Rawlins EDI Consulting
http://www.metronet.com/~rawlins/

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

Last Updated 1/11/2000

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

Proposed Consensus:  All other requirements asided, maximum interoperability between ebXML applications has
higher priority than maximizing interoperability with existing EDI implementations.  However, having an initial
solution within six months is also a high priority.  If the former can't be achieved within six months and the
latter can, then the latter has higher priority.

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.