There are changes marked that
are common between both of these documents though that are not part of the
state table changes. What are those reflecting?
Marc Goodner
Technical Diplomat
Microsoft Corporation
Tel: (425) 703-1903
Blog: http://spaces.msn.com/mrgoodner/
From: Doug Davis
[mailto:dug@us.ibm.com]
Sent: Tuesday, May 16, 2006 2:40 PM
To: ws-rx@lists.oasis-open.org
Subject: RE: [ws-rx] Groups - WS-RX TC Weekly Meeting modified
The version of
the doc I put out was just for the discussion around the state tables - which
as yet to happen.
Yes, Gil's
version needs to be resolved before the editors can continue their work.
-Doug
Part
of the problem here is that we have been asked to review two different versions
of WD13 at the same time. Is the emphasis now on just the documents you posted
for i093? Is this something that needs to be resolved before the editors can
start getting the pending issues applied to a single document for the TC to
review?
Marc
Goodner
Technical
Diplomat
Microsoft
Corporation
Tel:
(425) 703-1903
Blog:
http://spaces.msn.com/mrgoodner/
From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com]
Sent: Tuesday, May 16, 2006 12:45 PM
To: Doug Davis; ws-rx@lists.oasis-open.org
Subject:
RE: [ws-rx] Groups - WS-RX TC Weekly Meeting modified
+1 to this. I am concerned that I haven't seen any discussion on
the list about the numerous changes that went in i093. I can only conclude that
nobody has reviewed them :-(
- gp (missing Paul Cotton because I *know* he would have reviewed
them by now)
From: Doug Davis [mailto:dug@us.ibm.com]
Sent: Tuesday, May 16, 2006 8:44 AM
To: ws-rx@lists.oasis-open.org
Subject:
Re: [ws-rx] Groups - WS-RX TC Weekly Meeting modified
Paul - can you put i093 on the list of topics? We need an "ok"
from the TC before the editors formally make all of the changes as suggested by
the issue. Right now its holding up all changes to the spec and people
are supposed to be reviewing it [1].
-Doug
[1] http://www.oasis-open.org/apps/org/workgroup/ws-rx/email/archives/200605/msg00117.html
WS-RX TC Weekly Meeting has been modified by Mr. Paul Fremantle
Date: Thursday, 18 May 2006
Time: 01:00pm - 02:30pm PT
Event Description:
Dial-in: Thanks to Bob Freund/Hitachi
Tel: 1-866-705-2554 or
Tel: 1-913-227-1201 (Kansas)
Participant Passcode: 155640
Press *6 to mute or "un-mute" line.
IRC/Q Mgmt(thanks to DougD): http://webconf.soaphub.org/conf/room/wsrx
Agenda:
1) Roll Call
2) Review and approval of the agenda
3) Approval of minutes:
May 10th 2006
Preliminary minutes: http://www.oasis-open.org/apps/org/workgroup/ws-rx/email/archives/200605/msg00155.html
4) TC Schedule
5) AI Review
http://www.oasis-open.org/apps/org/workgroup/ws-rx/members/action_items.php
6) New issues since last conf-call
Wait for email.
7) Issue Discussion:
i119 When to piggy-back
RM headers
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i119
i089 suggest the restricted use of anonymous URI
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i089
i115 "must
understand" attribute for extensions to RM components
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i115
i121 security threats and requirements
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i121
i122 security profiles
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i122
8) Any other business
Minutes:
This event is one in a list of recurring events.
Other event dates in this series:
Thursday, 06 April 2006, 01:00pm to 02:30pm PT
Thursday, 13 April 2006, 01:00pm to 02:30pm PT
Thursday, 20 April 2006, 01:00pm to 02:30pm PT
Thursday, 27 April 2006, 01:00pm to 02:30pm PT
Thursday, 04 May 2006, 01:00pm to 02:30pm PT
Thursday, 11 May 2006, 01:00pm to 02:30pm PT
Thursday, 25 May 2006, 01:00pm to 02:30pm PT
Thursday, 01 June 2006, 01:00pm to 02:30pm PT
Thursday, 08 June 2006, 01:00pm to 02:30pm PT
Thursday, 15 June 2006, 01:00pm to 02:30pm PT
Thursday, 22 June 2006, 01:00pm to 02:30pm PT
View event details:
http://www.oasis-open.org/apps/org/workgroup/ws-rx/event.php?event_id=11212
PLEASE NOTE: If the above link does not work for you, your email
application may be breaking the link into two pieces. You may be able to
copy and paste the entire link address into the address field of your web
browser.