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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-core message

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


Subject: Re: Comments on ebXML Methodology: Core Components Discovery andAnalysis


Generally I agree with this discussion on perspective terminology  --
Business Document(s) are Message Payload(s).

I will point out however, from the Message Service perspective, the Message
Payload(s) can be anything  -perhaps just
a single binary thing like an image. In this case, from the BP/CC
perspective, "Business Document" is a significant abstraction.

Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074



Philip Goatly <philip.goatly@bolero.net> on 03/27/2001 02:11:05 AM

Please respond to Philip Goatly <philip.goatly@bolero.net>

To:   Bob Haugen <linkage@interaccess.com>, "'William J. Kammerer'"
      <wkammerer@foresightcorp.com>, James Whittle
      <james.whittle@e-centre.org.uk>
cc:   ebXML Core <ebxml-core@lists.ebxml.org>
Subject:  Re: Comments on ebXML Methodology: Core Components Discovery and
      Analysis



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
>


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-core-request@lists.ebxml.org




[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