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


attached is the full agenda for today's call

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


Title: Draft Agenda to WSRM TC Conference Call – May 06, 2003

Full Agenda WSRM TC Conference Call – Feb 24, 2004

 

The meeting of the WSRM TC took place by teleconference 
Tuesday Feb 24 2004, from 5:30 to 6:45 PM Eastern Standard Time
(UTC - 5)
 
Conference call Dial-in number : Toll number (only): 1-512-225-3050 Participant code: 89772

0         Draft Agenda:

Draft Agenda to WSRM TC Conference Call

1 Roll Call

2 Minutes Discussion

2.1 Appointment of Minute Taker

2.2 Approval of previous meeting minutes – 

3 Discussion of New Orleans Meeting and Conference papers

4 Discussions of Issues

5 Discussion of Editorial Comments

6 Discussion of Document Progression

 

Agenda approved

1         Roll Call

Attendance:

 Meeting ?? quorate.

2         Minutes Discussion

2.1      Appointment of Minute Taker

Tom Rutt will take minutes.

 

Minutes will serve to record issue resolutions.

2.2      Approval of previous meeting minutes

http://www.oasis-open.org/apps/org/workgroup/wsrm/download.php/5630/MinutesWSRMTC021704.htm 
 
xx  moved to accept the Feb 17 minutes. yy  seconded.
 
?? opposition, 2/17  minutes ??approved.

 

3         Discussion of New Orleans Meeting and Conference

Tom stated he told the OASIS staff that we wanted to meet all day Wednesday, and Thursday morning for our F2F.  This has been verified.

 

 

4         Discussion of Issues

 

4.1      Rel 108/115 Semantics of Polling and Fault Returns

 

 

Excerpt of new text:

2.x Response element

A receiver MUST include the Response element to indicate Acknowledgments for reliable messages and indications of reliable message Faults . This element includes the following attributes:

o        SOAP mustUnderstand attribute with a value of “1”

o        a ReplyPattern attribute, which defaults to the value “Response”

At least on of the following child elements MUST be present in the Response element:

o        NonSequenceReply element, which can have zero or more occurances

o        SequenceReplies element, which can have zero or more occurances

When the response is using the callback reply pattern, if the reply and the new request share a common destination URI, a Response element can coexist with a Request element, enabling the combination of an Acknowledgment message with the business response to the original message. This coexistence also enables a receiver sending another independent message to the sender with an Acknowledgment message (e.g., to reduce network traffic).

Table 14 Response Element

Cardinality

0 or 1

Value

None

Attributes

MustUnderstand

replyPattern

Child elements

NonSequenceReply

SequenceReplies

Fault

None

xample 7 shows an example of the Response element.

 

Example 9 Response Element

<Response

xmlns="http://www.oasis-open.org/committees/wsrm/schema/1.1/SOAP1.1"

xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

soap:mustUnderstand="1">

   <NonSequenceReply groupId="mid://20040202.103832@oasis-open.org/">

   <NonSequenceReply groupId="mid://20040202.103811@oasis-open.org/" fault="wsrm:PermanantProcessingFaulure"/>

   <SequenceReplies groupId="mid://20040202.103807@oasis-open.org/">

<RangeReply from="1" to="4"/>

<RangeReply from="5" to="5" fault="wsrm:InvalidMessageHeader"/>

<RangeReply from="6" to="42"/>

   </SequenceReplies>

</Response>

 

  (1) replyPattern attribute

If the response Element is being returned as a result of a poll request, this attribute must have the value “Poll”.

If the response is being returned as a reliable message callback, to return replies sent using the Callback reply pattern, this attribute must have the value “Callback”.

If the response is being returned using the Response reply pattern, this attribute indicate the “Response” value, which is the default for this attribute. In the case of a response returned using the Respose reply pattern, the following restrictions apply:

·         If the group does not use sequence numbers, the first element of the response must be a NonSequenceReply element containing the groupID which is the message ID for the reliable messaging Request.

·         If the group uses sequence numbering, the first element of the response must be a SequenceReplies element, with its groupID equal to that of the request, and with its first Range element having its from and to attributes both equal to the sequence number in the request.

 

 

4.2      Rel 113 Message Delivery processing after Fault.

 

 

4.3      New issue on elimination of Message Header on Request

 

 

 

4.4      Issue 49 WSDL Annotation

.

 

4.5      Soap fault for missing reliability features in request

 

 

4.6      Clarification Issue on Service enforcement of agreement

 

 

4.7      Sunil new Issue on Callback for Poll Request

 

  • New Issue
    From Sunil Kunisetty <Sunil.Kunisetty@oracle.com> on
    24 Feb 2004 00:50:10 -0000

 

 

5         Discussion of Editorial Comments.

Editorial Comments for Discussion

 

6         Timing of WS-Reliability progression

Timeline proposed at F2F meeting.

  1. Feb 10   Tuesday call, final editing instructions agreed.
  2. Feg 12 – Document posted for TC internal review.
  3. Feb 24 – TC review comments resolved, editing instructions produced.
  4. Feb 25  Frozen document completed, TC review begins.
  5. March 2 – CD 1 ballot closes
  6. March 5 – 30 day Review initiated
  7. April 5 – 30 Day public Review ends
  8. April 15, submit to oasis staff for member vote
  9. May 01– Membership two week review
  10. May 15  – start member two week vote
  11. May 30 - member vote concludes.  Earliest Oasis Standard.

 



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