[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Thursday AM prelim Minutes for WSRM TC F2F
The prelim minutes for Thurs AM are attached. -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133
|
1 Agenda Review and RefinementDraft Agenda: 1 Agenda Review and Refinement 2 Roll Call 3 Minutes Discussion 3.1 Appointment of Minute Taker 3.2 Approval of previous meeting minutes 4 Action Item Status Review 4.1 Action 121404-2 (Anish) Open 4.2 Action 012505-1 (Tom Rutt) Pending 4.3 Action 020805-2 (Tom Rutt) open 5 Status of WS-Reliability Specification 6 PAS Progression Discussion 7 Charter discussion 8 Next Step Documentation 8.1 Finalization of Errata 8.2 Future Enhancement Requests 8.3 Implementation Guidelines 9 Scheduled Vote to post Errata as CD 10 Composability with other WS-Specs 10.1 Composability Analysis 10.2 WS-Reliability and WS-Security Composition 10.3 Discussion of Liaison with WS-RX TC 11 Future Meeting Discussion 2 Roll Call
3 Minutes Discussion3.1 Appointment of Minute TakerTom Rutt agreed to take the minutes 3.1 Approval of previous meeting minutes
http://www.oasis-open.org/apps/org/workgroup/wsrm/download.php/12300/Minutes%20WSRMTC040505.htm Bob F moved to accept minutes. Anish Seconded. No opposition , minutes approved. 4 Action Item Status Review4.1 Action 121404-2 (Anish) OpenAction: Oracle will provide examples of soap header dumps with both ws-reliability and ws-Security headers in use, as in the interop demo. Anish posted email: WSS and WS-Reliability header dumps Anish Karmarkar 24 Feb 2005 23:22:27 Anish may post some additional examples of other combinations. Leave open 4.2 Action 012505-1 (Tom Rutt) PendingAction: Tom will investigate how to change the status of printed document. The posted standard still states CD. Continuing action, need standard number from OASIS staff 4.3 Action 020805-2 (Tom Rutt) openAction: Tom will investigate how to post the three OASIS pas documents on our server. Jamie Clark is investigating how to get the documents on the OASIS Site. 5 Status of WS-Reliability SpecificationChair’s Goal: finalize Cover Page and footers for official posting of standard. Above URL for proposed document for posting. Jamie will give final cover page by end of f2f Meeting. 6 PAS Progression DiscussionChair’s Goal: determine whether TC wants to continue to push OASIS staff to progress WS-Reliability 1.1 as ISO/IEC JTC1 standard through OASIS PAS process. Jamie Clark has confirmed that we can post the PAS documents associated with OASIS. PAS status is a class that JTC1 grants in 6 month increments. OASIS will continue to have PAS status until at least the end of 2005. After that OASIS will revisit the issue as to whether we will keep the status. Jamie stated that the OASIS Liaison policy states that OASIS can decide to send specs to outside bodies. There are several ways, to send OASIS docs to orgs: - OASIS keeps control of evolution, - OASIS will transfer Control of evolution The WSRM TC has asked that OASIS staff consider submitting ws-reliability as the first type of PAS doc (OASIS keeps maintenance responsibility). Two EBxml standards have been progressed as ISO standard (15000 parts 1 thru 5) Jamie asks that we read the Liaison rules. http://www.oasis-open.org/committees/liaison_policy.php Tom asked whether we should continue to pursue the PAS progression of WS-Reliability. Anish stated there is no need to change our course as of this time. Tom: If we do nothing, OASIS will continue to pursue progression thru PAS process as full ISO standard. Concensus to let OASIS staff continue work to progress WS-Reliability 1.1 as an ISO standard, with OASIS controlling the maintenance. 7 Charter discussionChair’s goal: discuss the future activities of the WS-RM TC, and possible charter Amendments to enable these activites. Defer until after discussion of the Future enhancements list..
11:00 Reconvene without bridge 8 Next Step Documentation8.1 Finalization of Erratahttp://www.oasis-open.org/apps/org/workgroup/wsrm/download.php/11868/ws-Reliability-Errata-ED0.1.htm Chair’s goal: finalize errata, in preparation for Vote to post as CD in afternoon session. Section1 was agreed to be included in the errata. Section 2.1.1: Jacques: clarification is that the tables should be read line by line. Jacques and Pete agreed to recast the tables in a more clear format and distribute as a new errata for vote. Section 2.1.2: Agreed to change offending sentence to: Errata Change offending sentence
to: “ In case GuaranteedDelivery
is not required, remove the group immediately. Otherwise, remove it if every message
has either been acknowledged or faulted “ Section 2.1.3: Agreed to change offending sentence to: “ Remove the group after every message has either been acknowledged
or faulted.”
1:00 PM: Next step docs continued 8.2 Future Enhancement RequestsChair’s Goal: review the futures list above, to prioritize potential enhancements required by industry. 8.3 Implementation GuidelinesChair’s Goal: determine progression plan for above document Agreed that 1.1 and 1.4 are not of concern, and should be removed from the next version of this implementers guide. Agreed to discuss 1.2 and 1.3 at the meeting. 3:00 PM Break 9 Scheduled Vote to post Errata as CDChair’s Goal: vote errata (as edited in morning session) to CD status, and post on OASIS web site as referenced from posted ws-reliability standard. 10 Composability with other WS-Specs10.1Composability AnalysisChair’s goal: release an edited version of the above document for widespread review inviting comments from other OASIS TCs and W3C WGs. 10.2WS-Reliability and WS-Security Compositionhttp://www.oasis-open.org/apps/org/workgroup/wsrm/download.php/10944/WS-R%20WS-Security-Draft.pdf Chair’s goal: Given no comments have been posted, discuss progression plans for the above document. 10.3Liaison with WS-RX TC11 Future Meeting DiscussionChair proposal: Resume bi-weekly Tuesday 5:30 PM 90 Minute meetings starting May 17. Leave Next F2F timing and location TBD. 5:00 Bridge Closes, meeting scheduled to adjourn. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]