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: Trading Partner Agreement definitions


Rik

FYI, the definitions you used below are now obsolete as they have been
incorporated with a few variations in the latest TP requirements documents
published by Marty as follows ...

1. Document. A Document is any data that can be represented in a digital
form.
2. Party. A Party is a company, organization or individual or other entity
that can generate, receive or relay Documents.
3. Party Profile (PP). A Party Profile is information about a Party that can
be used to determine the alternative ways to send documents to that Party. A
Party Profile also defines the supported Processes and associated Service
Interfaces along with the technology capabilities for each Service
Interface. A Party Profile may be represented as a Document.
4. Party Agreement (PA). A Party Agreement is information agreed between two
(or more) Parties that defines how they will exchange Documents. A Party
Agreement may be represented as a Document.
5. Partner Agreement. A Partner Agreement is a Party Agreement that is
designed to be used for Commerce. A Partner Agreement may be represented as
a Document.
6. Partner. A Party to a Party Agreement.
7. Party Discovery Process. A process by which one Party can discover Party
Profile information about other Parties.
8. Service Interface. A Service Interface is the representation, in the PP
and PA, of the services provided by a given Party. A Party may group the
services into more than one Service Interface when appropriate.

Are these now OK?

David

-----Original Message-----
From: Rik Drummond [mailto:rvd2@worldnet.att.net]
Sent: Tuesday, September 26, 2000 9:29 PM
To: A.J. (Tony) Blazej; Burdett, David; 'Martin W Sachs/Watson/IBM';
ebxml-tp@lists.ebxml.org
Cc: ebxml-transport@lists.ebxml.org
Subject: RE: Trading Partner Agreement definitions


see edits below... rik

-----Original Message-----
From: A.J. (Tony) Blazej [mailto:ablazej@openapplications.org]
Sent: Sunday, September 10, 2000 3:52 PM
To: Burdett, David; 'Martin W Sachs/Watson/IBM';
ebxml-tp@lists.ebxml.org
Cc: ebxml-transport@lists.ebxml.org
Subject: Trading Partner Agreement definitions


This is helpful - once you all [the experts] agree, this should be made part
of glossary!
Tony Blazej
Open Applications Group
At 03:40 PM 9/8/00 -0700, Burdett, David wrote:

>This might be a nit pick, but I do think that calling everything a "Trading
>Party Agreement" is confusing since:
>a) you might want to use the information for non-trade purposes
>b) there isn't always a prior agreement.
>
>I propose therefore the following draft definitions to facilitate a common,
>and clearer understanding:
>1. Document. A Document is any data that can be represented in a digital
>form.
>2. Party. A Party is a company, organization or individual or other entity
>that can generate, receive or relay Documents.
>3. Party Profile. A Party Profile is information about a Party that can be
>used to determine the alternative ways to send documents to that Party. A
>Party Profile may be represented as a Document.
>4. Party Agreement. A Party Agreement is information agreed between two (or
>more) parties that defines how ((, what, why, when)) they will exchange
Documents. A Party  *************
>Agreement may be represented as a Document.
>5. Trading Party Agreement. A Trading Partner Agreement is a Party
Agreement
>that is designed to be used for Commerce. A Trading Party Agreement may be
>represented as a Document.
>
>Thoughts?
>David




[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