[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [ebxml-msg] Decisions from the last call - work for next week
Team, In this weeks conference call the Requirements list was reviewed and the following work stack for next weeks meetings was created. Requirement Brief description Agreed action list number 7, 11 & 16 Encryption, compression, encoding Must agree a direction and relationship with and security WS-Security - Possible requirements or recommendations. 17 Align with BPSS Focus of meeting with BPSS & CPP/A 20 Sync Reply Decision and direction required - could signals only be mandatory? 21A Description of failure Low priority for F2F time. 1 SOAP 1.2 Only if raised by attendee. 3 Business interface/message service A small amount of time will be allowed. interface 18 & 18A Modularity This is an idea an philosophy. 21 Reliability This will be discussed if time allows. 22 Clustering If interest and time allows. 8 Mult-hop Need to decide scope does it add value? The following point was also raised. The use of the refToMessage ID needs clarification and has several items on the outstanding issues list. Any comments to this list please! Have a safe weekend and see some of you next week. Ian Jones Chair OASIS ebXML Messaging Services TC Tel: +44 (0)29 2072 4063 Fax: +44 (0)29 2072 4137 Email: ian.c.jones@bt.com ---------------------------------------------------------------- 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] | [List Home]