Resend - Updated Issues List - Straw Poll

[Mike Rawlins <rawlins@metronet.com>]

I forgot the attachment the first time...

--------------------------------
Folks,

Here is the updated issues list.  I would like to get a straw poll
concerning where we stand.  I don't think that any of these proposed
consensus statements are perfect, but I would like us to find some that
are adequate.

Please send a vote to the listserv with subject "ebXML Requirements
Straw Poll".    Please send your vote in by close of business Wednesday,
January 19.

For my ease in tabulating votes,  please just list the numbers and
whether you agree or disagree with the consensus statement.  Such as:

Subject:  ebXML Requirements Straw Poll

1  Disagree
2  Agree
3  Agree
4  Agree

If you want to discuss your reasons, please do so in a separate e-mail.

Thanks,

Mike



--
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.