[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ebxml-cppa] planning version 1.1 edits: partyName
Not sure if this is the best way to distribute changes: I'm using our 1.0 spec as base and the following line numbers are referring to the attached document: line 583, 605-613, 687-688: New addition regarding partyName line 2437, 2573, 2651: added lines to Examples line 2785-2787: added lines to Dtd (I understand that Dtd is going away, I made the changes for the sake of consistency). line 3036-3037: schema All lines are highlighted, too. Thank you for reviewing! Any suggestions at all are welcome! Please do let me know if I missed anything. Jean -----Original Message----- From: Dale Moberg [mailto:dmoberg@cyclonecommerce.com] Sent: Tuesday, November 27, 2001 9:34 AM To: ebxml-cppa@lists.oasis-open.org Subject: [ebxml-cppa] Thursday, November 29,CPPA teleconference agenda: planning version 1.1 edits An important meeting for moving forward on emptying the issues database! Please send in additions, though you can see that we have a bountiful harvest already. Call in information: USA Toll Number: +1-712-884-0932 Toll Free Number: 877-719-1163 PASSCODES 305145 LEADER: Mr Brian Hayes Brian's cell phone number: (925) 788-6304 Proposed Agenda: 0. Administrative issues: a. January Face to Face needed? What week can people attend? Where can it be held? b. Writing schedule for December drafts of version 1.1 We need people to take ownership for drafting additions or changes for 1.1 revisions. Tony is on vacation this week, and we will need to find out that he can piece the edits together or whether he wants help. Shall we focus on parceling out tasks based on schema changes? And then add in all the residual tasks? If so, schema updates need to be available for review at the start of December. Arvola? Taking responsibility for sections, means checking examples involving the schema elements, noting any renumbering of sections (try to keep to the minimum), checking cross-references, checking whether other appendices need to be updated. 2. Service and Action naming proposals (Brian and Hima subteams) Using ActionBinding element to store long name and short names for actions. Using ActionBinding for storing Packaging specifics. ActionBinding usage allows specific reference to portions of a BPSS instance that are being agreed to (perhaps reducing need to "filter" out portions of document subject to agreement.) Volunteers for write-up? 3. PerMessage, duplicateElimination, AckRequested, signing, synch (and packaging related distinctions following synch/asynch response apportionment) (Arvola review) Volunteer for write-up? Residual issues: 4. PartyName, PartyRef changes, etc. (Marty and Jean) Volunteers? 5. Arvola Schema Straw Proposal: ready for schema? (Arvola) ActionBinding writeup? Arvola? Peter Ogden will handle writing assignment for CertificateRef related changes and additions. Arvola's "new elements" approach to be used, and not attributes qualifying certificate usages. 6. New SecurityDetails element discussion. Dale Moberg will write up this element. No word yet from XAML TC subgroup on whether policy notations usable in 1.1. Messaging says their policy appendix is probably stable. TrustAnchor element issues. Thanks to Brian Hayes and Commerce One for hosting tomorrow's CPPA teleconference. ---------------------------------------------------------------- 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