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


Help: OASIS Mailing Lists Help | MarkMail Help

wsrm message

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

Subject: Prelim minutes of wsrm tC meeting 7/12/2005

the prelim minutes are attached.

The next meeting will be Sept 6.

Tom Rutt

Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133

Title: Full Agenda for WSRM TC Conference Call –June 14, 2005

Prelim Minutes WSRM TC Conference Call –July 12, 2005


The meeting of the WSRM  TC took place by teleconference 

Tuesday, July 12, 2005, from 5:30 to 6:00 PM Eastern Standard Time

1       Draft Agenda:


    1 Draft Agenda to WSRM TC Conference Call

    2 Roll Call

    3 Minutes Discussion

    3.1 Appointment of Minute Taker

    3.2 Approval of previous meeting minutes –

    4 Action Item Status Review

    5 Status of WS-Reliability Specification

    6 Composability with other WS-Specs

   7 WS-RX Gap Analysis

   8 Next version of WS-Reliability

   9 Meeting schedule

   10 New business


2       Roll Call



First Name

Last Name





Voting Member

Hitachi, Ltd.*




Fujitsu Limited*




Fujitsu Limited*



TC Chair

Fujitsu Limited*



Voting Member

Hitachi, Ltd.*



Voting Member

Hitachi, Ltd.*



Voting Member

NEC Corporation*



Voting Member

Nortel Networks



Voting Member

Oracle Corporation*



Voting Member

Oracle Corporation*



Voting Member

SeeBeyond *




Sun Microsystems*



Voting Member

VeriSign *



Meeting was quorate.


3       Minutes Discussion


Tom Rutt Volunteered to take minutes.


3.1    Approval of previous meeting minutes


The minutes of the 6/28 teleconference meeting are posted at:



Alan Moved to approve the 6/28  minutes, Bob F seconded.


No opposition minutes 6/28  minutes are approved


4       Status of Action Items

4.1    Action 121404-2 (Anish) Open

 Action: 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.1    Action 012505-1 (Tom Rutt) Pending

Action: Tom will investigate how to change the status of printed document.  The posted standard still states CD.

Continuing action, sent newest version to OASIS Staff with Errata to post before last meeting. 


OASIS Staff has posted the documents at:



Leave action item open until the errata index pointing to the errata cd is posted as:


4.2    Action 042805-1 (Jacques Durand) Pending

Action: Jacques will post a new version of the composability analysis, to reflect discussions at the F2F meeting.


Jacques will post the new version soon for information.

5       Status of WS-Reliability Specification


The public and member web site pages for the TC to have a single announcement, which refers by URL to spec and  schema at the proper location on the OASIS web site.








OASIS Staff has posted the errata cd as:


However, on the posted standard the errata index is referenced as as:



The errata Index still does not yet exist.


The action item will stay open until the errata index page is posted.


6       Composability with other WS-Specs


WS-Security Composition paper from Fujitsu, Hitachi and NEC:

               WS-Reliabilty And WS-Security - First Draft  


The latest version of composability aspects is posted as:

                Composability Analysis (V0.5)


Jacques has an action item to post a version reflecting the f2f discussion.


Jacques stated that Fujitsu has done implementation of ws reliability and ws security as implemented in Java Open source.


Jacques stated they might contribute this as open source. 

7       WS-RX Gap Analysis

The WS-Reliability Requirements are posted at:



The output of a task force effort (version .8) was posted, after the last meeting, at: 




Anish created a requirements analysis (marking both ws-reliability and ws-reliable messaging against the ws-reliability requirements document) , which was posted as:




Anish stated the first gap analysis paper was submitted to the European conference on web services.


Open for discussion on our requirements clarification.

8       Next version of WS-Reliability

The working list of potential enhancements to WS-Reliability was posted after the last f2f as:



The TC needs to discuss if it will work on a next version of the ws-reliability spec.


It was agreed to put this on the agenda for this meeting


Tom Stated that we could wait a little while before we make a decision.  We could determine the progress of the WS-RX TC before we make a decision on this matter.


Jacques stated that EB MS version 3 is using ws-reliability.  Reliability on the response is a missing feature.


Iwasa: there are some requirements in Japan for reliability in the response.   This does provide a need for change of the specification.


Doug: the existing ws-rm specification treats the response as part of a separate reliable stream. 


Doug: it sounds like we are missing a driving need to do something.  I am not sure is these items are pressing whether or not ws-rx tc existed.


Iwasa: I think we need to define the http binding somewhere.  The version 2 spec could do it differently.


Tom: A question is, what would be the driving factor for a ws-reliability version 2.


Jacques: It still remains that there is not sufficient specification of reliability to synchronous responses.  It is slightly different than a request reliability assurance.


Jacques: we need a better assessment of what form of reliability is needed for synchronous response.  From there we could move forward.


Jacques: at the very least we should have a clear discussion on reliable response.  My concern is to have a well rounded spec to provide the same level of reliability for the request and the response.


Tom: If we had a contribution we could discuss it as part of this agenda item.


We will put on agenda for the Sept 6 meeting.

9       Future meeting schedule

Last biweekly teleconference is scheduled for July 12.


TC agreed at last meeting to take a break from having bi-weekly meetings, with the next

Teleconf taking place on September 6, 2005.  The future schedule can be determined at that meeting.


10        New Business

Bob F moved to adjourn, Doug B seconded.



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