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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

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

Subject: Re:RE: Regarding the Thursday ebXML Conf Call


    What was presented to us during our call today was that you were selecting
mime as "the" ebXML solution.  If that is not the case, then we don't have an
issue.  Although I personally can't understand why anyone would want to use an
antiquated technology such as e-mail to forward XML, especially in a business to
business exchange, I do see the need to accomodate folks desires.  If on the
other hand, you are selecting mime as "the" ebXML solution, then I think that
you will loose participation and support of the bulk of the XML community.  

Mark Crawford
Research Fellow
LMI Logistics Management Institute
2000 Corporate Ridge, McLean, VA 22102-7805
(703) 917-7177   Fax (703) 917-7518
"Opportunity is what you make of it"

____________________Reply Separator____________________
Subject:    RE: Regarding the Thursday ebXML Conf Call 
Author: "Dick Brooks" <dick@8760.com>
Date:       3/2/00 2:12 PM

Rik, it appears the Requirements group needs to be made aware that people
will want to send XML documents via E-mail and E-mail is not a W3C


-----Original Message-----
From: owner-ebxml-transport@lists.oasis-open.org
[mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of Kit
(Christopher) Lueder
Sent: Thursday, March 02, 2000 1:30 PM
To: Rik Drummond; Ebxml Transport
Cc: Mike Rawlins; Mark CRAWFORD
Subject: Regarding the Thursday ebXML Conf Call

Regarding the EBXML Transport/R/P conference today, my understanding is
that the group is pursuing a mime-based envelope structure? I mentioned
that at the EBXML Requirements teleconference, which happened to be
immediately after the TRP teleconf, and they weren't happy about that
direction and hoped the TRP group will revisit that decision. In
particular, it was suggested that there is an EBXML requirement for all
EBXML specifications to be compliant with W3C technical specificatons.
(Though Mike Rawlins said that the transport may be an exception.) I
cite the relevant section from the EBXML Requirements document, which is
to be released to the full EBXML body for review this Monday.


1.2.1 ebXML Vision
The ebXML vision is to deliver:

"A single set of internationally agreed upon technical specifications
that consist of common XML semantics and related document structures to
facilitate global trade."

This single set of ebXML technical specifications will create a Single
Global Electronic Market.  To create this single global electronic
market, this single set of ebXML technical specifications:

 - is fully compliant with W3C XML technical specifications holding a
recommended status,
 - provides for interoperability within and between ebXML compliant
trading partner applications,
 -  maximizes interoperability and efficiency while providing a
transition path from accredited electronic data interchange (EDI)
standards and developing XML business standards, and
 - will be submitted to an appropriate internationally recognized
standards body for accreditation as an international standard.

    _/    _/             Kit C. J. Lueder
   _/   _/         _/   The MITRE Corp.         Tel:  703-883-5205
  _/_/_/    _/  _/_/_/ 1820 Dolley Madison Bl  Cell: 703-577-2463
 _/   _/   _/    _/   Mailstop W658           FAX:  703-883-3383
_/    _/  _/    _/   McLean, VA 22102        Mail: kit@mitre.org
Worse than an unanswered question is an unquestioned answer.

[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