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: Full Agenda for 4/4 Teleconf

The full agenda, with links is attached

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

Full Agenda WSRM TC Conference Call –April 4, 2006


The meeting of the WSRM  TC will take place by teleconference 

Time         Tuesday, 24 Jan 2006, 05:30pm to 06:30pm ET

Description            Host: Fujitsu

Toll only : 1-512-225-3050

Participant code: 375491


1          Draft Agenda:

1) review agenda

2) Roll Call

3) Minutes approval

4) Action Items

5) Discussion of potential TC future activities

5.1 Reliability of Response

5.2 Delivery Assertions for Sequences

5.3 Interworking WS-Reliability and WS-Reliable Messageing

5.4 OASIS IPR Status for TC

6) New Business

2          Roll Call



Meeting ?? quorate


3          Minutes Discussion


Tom Rutt Volunteered to take minutes.


3.1       Approval of previous meeting minutes


The minutes of the 2/21 teleconference meeting are posted at:



xx moved to approve the 2/21  minutes, yy  seconded.


?? opposition minutes 2/21  minutes ?? approved


4          Status of Action Items

2006-02-21-1 - Closed

Action: Tom will post a contribution on interworking ws-reliablity with ws rm.



Action: Jacques will clarify what he thinks we should do on reliability of req-resp.


2006-02-21-3 - Closed

Action: Iwasa will try to find out what da levels are being used for ws reliability.


5          Discussion of Potential Future TC activites

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




TC needs to decide among the following possibilities

  1. work to resolve new issues raised within charter of TC,
  2. put the tc into maintenance mode (i.e., two meetings a year awaiting usage issues),
  3. schedule vote to disband TC


5.1       Reliable Request Response

Jacques posted the following contribution before the last meeting: Reliability of Request-Responses



5.2       Delivery Assertions for Sequences

Fujitsu posted a contribution in January:


Which included the following sub- proposal:

Develop a high level specification for delivery assurance/QoS of a

reliable message.   We need to define the notion of reliable message

delivery assurance in the context of QoS by describing the precise

semantics (but not the syntax or protocol).  The standardization of the

expression of delivery assurance could be used to support either WS-R or

WS-RMg (WS-RX).*


We believe that a "mark-up" of the standard representation of delivery

assurance would be very valuable for the WS industry and would be more

expediently developed, generated and approved in the WSRM TC (vs WSRX

TC) due to its proposed sharper focus.


For example, we recommend distinguishing between an acknowledgement from

the receiving RMg entity (e.g. in WS-RX spec) vs an acknowledgement that

confirms that the layer above the receiving RMg entity (perhaps a WS

control protocol or application layer) has correctly received the

message from the RMg entity.


Also, there may be different notions of the various forms of reliable

message delivery: at least once, atmost once (AKA duplicate

elimination), guaranteed delivery, sequential delivery, etc.  What do

these notions really mean to the layer above?  They need to be precisely

defined and illustrated.


Iwasa posted the following Email::


Here is my action item in the last telecon.


Action: Iwasa will try to find out what da levels are being use for ws reiliialbiy.


As far as I know, there are two industry groups that are implementing WS-Reliability in Japan.

Both industry groups are implementing Delivery Assuarance, but neither Duplicate Elimination

nor Ordered Delivery at this point.






5.3       Interworking WS-Reliability and WS-Reliable Messaging

Tom R posted the following Email, outlining an Interworking unit for WS-Reliability and WS-Reliable messaging.:




5.4       OASIS IPR Status of TC

Tom Rutt forwarded the following email, from Jamie Clark, as:


    * From: James Bryce Clark <jamie.clarkAToasis-open.org>

    * To: tomATcoastin.com

    * Date: Tue, 21 Feb 2006 16:04:03 -0800


     As you know, our current OASIS IPR Policy was adopted in April 2005

with a 2-year transition period, during which the OASIS TCs then existing

could choose when to convert from the old IPR Policy to the new one under

the OASIS IPR Transition Policy [1].  As we announced back in 2005 [2],

each TC has until April 2007 to select one of the new policy's three

licensing IPR Modes, and conduct the transition vote;  or cease operations

if no transition vote is successfully completed by April 2007.


    Tom, it would be helpful to know whether your TC has discussed plans to

convert.   Could you please advise back to me whether your TC has begun

considering this, and if so, roughly on what schedule?  This is an informal

inquiry:  we are asking only for current thinking, not a binding

determination or TC member poll.  The level of answer we hope for is:


     __ We haven't considered our timing yet.

     __ We are considering starting a transition roughly in ___ [calendar quarter] 2006/07

     __ We probably will close before April 2007 and not convert.


If planning has not started, OASIS standards development staff will be in

touch to discuss your TC's plans, needs and timing between now and the

OASIS Symposium in San Francisco in May.  Obviously we will be happy to assist.


Thanks for your attention and assistance.

Best regards  Jamie Clark


~   James Bryce Clark

~   Director, Standards Development, OASIS

~   jamie.clark@oasis-open.org


[1] http://www.oasis-open.org/who/ipr/ipr_transition_policy.php

[2] http://lists.oasis-open.org/archives/members/200502/msg00006.html



6          Future Meetings

At last meeting, TC agreed to decide on the next meeting at this meeting. 



7          New Business

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