[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Addition to 20040729-wsn-minutes- we missed start of Thursday's meeting!
In reviewing all 3 sets of minutes from the WS-N f2f meeting, I noted that the first one (from Brian and Jem) did not include the start of Thursday's meeting.
http://www.oasis-open.org/archives/wsn/200407/msg00084.html
It picks up with Peter presenting his WS-RF dependency slides. We missed the first hour or so of the morning meeting.
The following text is proposed to supplement/ augment the Minutes of July 29.
In item 3. below, I did not record who made the motion on initial termination time, or who seconded, or if the motion was approved by acclamation (no dissent) or vote. But I recall the motion was approved. Also, I did not record who said what, but captured the essence of the discussion of this issue.
alan
WS-N TC Minutes -from 9:30AM on 29 July 2004
1. Review of Action Items from last WS-N telecon- all closed
2. Status of drafts (stable, working, change summary) for WS-Base Notification, WS-Topics, and WS Brokered Notification
-Change Summary text (delta from "stable draft" text) is now available for WS-Base Notification, WS-Topics, and WS Brokered Notification
-Work-in-Progress (AKA "editors") draft text is in a separate folder from "stable draft" text.
-URIs will change for each new draft text (old draft text not deleted, but has different URI
3. Issue 2.3: Duration for initial termination time is not allowed in WS-Base Notification
WS-Base Notification specifies an absolute termination time, but not the duration of the subscription.
Discussion:
-How much control does subscriber need to end the subscription?
-Is this a WS-RF issue, i,e model subscription as a resource and specify its lifetime as a duration in WS-RL?
-How much sould WS-Base Notification be dependent on WS-RF?
-Is a subscription really a resource? If not, then we can't use WS-RL to specify termination time of any type.
-Confusing to have to subscribe using one spec (WS-Base Notification) and unsubscribe using another spec (WS-RL)
-Need to be able to renew the subscription (i.e. unpublished WS Renewable References or WS-RL?)
-Absolute time introduces problems of unsynchronized clocks and clock skew between sender and receiver (of the Subscribe Request message)
Action: Add optional capability to specify initial termination time, in WS-Base Notification, as a duration, rather than an absolute termination time.
Note that these two options are mutually exclusive.
[AW Note: This still leaves open the issue of whether you could also use WS-RL to terminate the subscription by specifying its lifetime in that spec. In that case, you could conceivably have a race condition/ ambiguity, where subscription termination could be done in both specs with different termination times]
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Peter then presented his slides on WS-N spec dependency on WS-RF specs, in preparation for discussion of issue 2.2
[I have the notes from this presentation, but I suggest we supply the url from OASIS WS-N web site email archives]
Jem's uploaded minutes pick up from here.
Alan Weissberger
1 408 863 6042 voice
1 408 863 6099 fax
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]