Re: Comments on ebXML Methodology: Core Components Discovery andAnalysis

[Philip Goatly <philip.goatly@bolero.net>]

Hi there,
   For what it is worth.

   At Bolero.net we have come to a similar conclusion:

   1. A business Document is the data payload. It does not of course
necessarily mimic a paper based 'Document'

   2. It becomes a message when it has a sender and receiver and all that is
required for the sending and receiving


Cheers, Phil Goatly

----- Original Message -----
From: "Bob Haugen" <linkage@interaccess.com>
To: "'William J. Kammerer'" <wkammerer@foresightcorp.com>; "James Whittle"
<james.whittle@e-centre.org.uk>
Cc: "ebXML Core" <ebxml-core@lists.ebxml.org>
Sent: Monday, March 26, 2001 5:22 PM
Subject: RE: Comments on ebXML Methodology: Core Components Discovery and
Analysis


> William J. Kammerer:
> >In order to
> >not confuse people, might I suggest simply calling a business message a
> >"Business Message"?
>
> In ebXML, "message" means the whole package transported
> by the Messaging Service (used to be TR&P).  Some people
> (including me) have taken to calling the payload the "Business
> Document".  I know this differs somewhat from trad EDI lingo,
> but I think it is the most consistent usage within ebXML.
>
> -Bob Haugen
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: ebxml-core-request@lists.ebxml.org
>