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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-tp message

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


Subject: FW: Trading-Partner Requirements document


FYI

*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************
---------------------- Forwarded by Martin W Sachs/Watson/IBM on 10/04/2000
11:44 AM ---------------------------

Tony Weida <TonyW@EDIFECS.COM> on 10/04/2000 11:00:48 AM

To:   Martin W Sachs/Watson/IBM@IBMUS
cc:
Subject:  FW: Trading-Partner Requirements document



Hi Marty,

Could you please forward this to the TP list?  It was rejected by the
server, I think, because I'm subscribed as weida@edifecs.com, but my mail
goes out under tonyw@edifecs.com.  Sometimes I hate computers :-)

Thanks,
Tony

>  -----Original Message-----
> From:   Tony Weida [mailto:weida@edifecs.com]
> Sent:   Wednesday, October 04, 2000 10:49 AM
> To:     Martin W Sachs/Watson/IBM; ebxml-tp@lists.ebxml.org
> Subject:     RE: Trading-Partner Requirements document
>
> Some comments on the requirements document ...
>
> General
>
> The document frequently refers to processes, sometimes qualified as
> application process, discovery process, internal process, back end
> process, bilateral process, business process or non-business process.  It
> would be helpful to agree on a small, consistent set of names and
> definitions for "process" and related terms.  I'd be glad to work on
that.
> As an example, I like to think of internal (business) processes
> interacting by means of a (business) collaboration protocol:  Each
> business collaboration protocol prescribes a particular set of
> interactions between two or more internal business processes operated by
> independent business entities that collaborate to reach common or
> complementary goals.  This terminology is consistent with the ebXML
> Business Process Metamodel.
>
>
> Introduction
>
> p 1, The purpose ... is to define the requirements for the "Party
Profile"
> and "Party Agreement" (not just Party Profile)
>
>
> Definitions
>
> p 2, definition 6 (Partner): Should say "A party that is involved in a
> Partner Agreement." (not Party Agreement)
>
> As mentioned above, process and related terms should be individually
> defined.
>
>
> Requirements
>
> There are two separately numbered sets of requirements, the first for
> specification of documents, and the second for the overall specification.
> For convenient reference, I'd prefer to have a unique identifier for each
> requirement (either by using a single numeric sequence, or by uniquely
> prefixing each separately numbered subset of the requirements).
>
> p 4, specification requirement 7: should say "a predefined model of an
> Application Process"  (as the term is used in the requirements doc), not
> process in general.
>
>
> Ideas for Later Phases
>
> Idea 8: As an example of multiple service interfaces, I'd say "A single
> service interface might include ..."
>
> Respectfully,
> Tony Weida
> Edifecs Commerce
>
> > -----Original Message-----
> > From: Martin W Sachs/Watson/IBM [mailto:mwsachs@us.ibm.com]
> > Sent: Tuesday, October 03, 2000 3:50 PM
> > To: ebxml-tp@lists.ebxml.org
> > Subject: Trading-Partner Requirements document
> >
> >
> > I have attached the latest version of the Trading-Partner Requirements
> > document.
> >
> > Since no comments were received on the prior version, the changes
> consist
> > only of a few minor wording changes and two new explanatory paragraphs
> for
> > Requirements numbers 4 and 5.
> >
> > I expect that we can ratify this document at the face-to-face and move
> on
> > to beginning to produce a specification.
> >
> > Regards,
> > Marty
> >
> > (See attached file: partner-requirements.doc)
> >
> > ******************************************************************
> > *******************
> >
> > Martin W. Sachs
> > IBM T. J. Watson Research Center
> > P. O. B. 704
> > Yorktown Hts, NY 10598
> > 914-784-7287;  IBM tie line 863-7287
> > Notes address:  Martin W Sachs/Watson/IBM
> > Internet address:  mwsachs @ us.ibm.com
> > ******************************************************************
> > *******************
> >
> >  << File: partner-requirements.doc >>





[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