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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-cppa message

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


Subject: Re: [ebxml-cppa] Re: **VOTE** BPSS/CPPA issue - #19 (old)


+1

Martin W Sachs wrote:

> I agree with this proposed change.
> 
> Don't forget to put the RFC2119 words in capitals.
> 
> Regards,
> Marty
> 
> *************************************************************************************
> 
> 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
> *************************************************************************************
> 
> 
> 
> David Smiley <dsmiley@mercator.com> on 12/13/2001 10:21:42 AM
> 
> To:    ebTWG-BPS <ebtwg-bps@lists.ebtwg.org>, ebXML-CPPA
>        <ebxml-cppa@lists.oasis-open.org>
> cc:
> Subject:    **VOTE** BPSS/CPPA issue - #19 (old)
> 
> 
> 
> No substantive responses have been received that require
> modifying the proposed change to the specification.
> 
> Your vote is needed.
> 
> **Do you agree with the proposed change?**
> 
> FYI,
> Once approved, the resolution goes into the
> BPSS Issues Log (Pallavi). Then, an editor will be assigned
> to make the changes to the spec prescribed by the resolution.
> 
> *************************************************************
> Old/New issue: Old
> Re-numbered for V1.1: 19
> Number: 27
> Date: 4/3
> Originator: QRT
> Line: 734-736 (Section 6.4.2.1)
> 
> Issue:
> A CPA need not use an ebXML business process.
> ebXML can be incrementally adopted.
> 
> Suggestion for Change to BPSS Spec:
> 
> The text of the specification is unchanged from
> V.99 to V1.01. In section 6.4.2.1, it reads:
> 
> "The CPA/CPP Specification requires that parties
> agree upon a Collaboration Protocol Agreement (CPA)
> in order to transact business. A CPA associates itself
> with a specific Binary Collaboration.
> Thus, all Business Transactions performed between
> two parties should be referenced through Business
> Transaction Activities contained within a Binary Collaboration."
> 
> Propose change as follows:
> 
> "The CPA/CPP Specification allows parties to agree
> upon a Collaboration Protocol Agreement (CPA)
> in order to transact business.
> A CPA may associate itself with a specific Binary Collaboration.
> Thus, Business Transactions performed between two parties
> may be referenced through Business Transaction Activities
> contained within a Binary Collaboration."
> 
> Issue Comments:
> 
> Background material:
> Some comments were posted against V0.99
> http://www.ebxml.org/project_teams/jdt/ts/SpecificationSchemaV0.99.pdf.
> 
> The current draft being revised is V1.01
> http://www.ebxml.org/specs/ebBPSS.pdf or
> http://www.ebxml.org/specs/ebBPSS.doc.
> 
> 
> David Smiley
> Director of Standards
> Mercator Software
> 540.338.3355
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.ebtwg.org/ob/adm.pl>
> 
> 
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
> 




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


Powered by eList eXpress LLC