OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-requirements message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: ebXML Requirements


Straw Poll
To: ebXML-Requirements@lists.oasis-open.org
Cc: turochas.fuad@ebay
MIME-Version: 1.0
Content-Type: MULTIPART/mixed; BOUNDARY=Troop_of_Baboons_968_000
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 

--Troop_of_Baboons_968_000
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: ZPXYSA6Rewn0G6oyNUb6wA==

Folks:

1  Agree
2  Agree
3  Agree
4  Disagree


Regards,
T


--Troop_of_Baboons_968_000
Content-Type: TEXT/plain; name="ebXML_Requirements_Issues_0113.txt"; charset=us-ascii
Content-Description: ebXML_Requirements_Issues_0113.txt
Content-MD5: dUGaIW2bHq4ee0FK4q2mKw==

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.






--Troop_of_Baboons_968_000
Content-Type: MESSAGE/rfc822; name=Mailbox
Content-Description: Mailbox

From <IMAP4.psuedo.sims> Tue Jan 18 11:05:47 2000
Date: Tue, 18 Jan 2000 11:05:47 -0800 (PST)
From: Postmaster
Subject: Message from mail server       
Content-Length: 96
Mime-Version: 1.0
Status: RO
X-IMAP: 948222347 1

Delete.
This is a system message.                                















--END+PSEUDO--


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC