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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsn message

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


Subject: WSN Policy initial allocations


For action of;
  Rick Cobb
  Matt Roberts
  Martin Chapman
  David Hull
  William Vambenepe
  Lily Liu

Following on from the conference call on 20th December '05 I took an action
item to make an initial allocation of people to the skeleton WSN Policy
document contents based on the ordered list voting from the face to face
last year.

I dug into the first six items on the list and allocated them as shown
below based on who looked at the idea the last time around.

For your allocated item, please formulate a description of the policy
option using the basic headings template described in 3.1 of [2]. I am
happy to receive recommendations for changes to the template if you think
it appropriate.

We will have a review of these items on the first call back in the New Year
(16th January).
Thanks in advance, and seasons greetings!

Matt


                                               VOTES
Durability, replay                              15
  - Durability proposal [1] submitted by Rick Cobb
  - Placeholder 4.12 in WSNP draft 1a [2].

Managing message rates                          14
  - Message rate discussion [3] submitted by Matt Roberts
  - Placeholder 4.11 in [2].

Boxcarring to conserve bandwidth                13
  - Proposal [4] submitted by Martin Chapman
  - Placeholder 4.10 in [2].
  - Note that this relates to part of the message rate proposal in [3]
  - (Matt to avoid stepping into boxcarring)

Advertising continuity support                  9
  - Use case [5] drafted by David Hull
  - Placeholder 4.9 in [2].

Selection of subtree from large message         7
  - WSN issue 6.2 (partial notifications) owned by William Vambenepe
  - Placeholder 3.4 in [2].

Establishing QoS                                7+
  - Clearly QoS could cover a number of things
  - Initially I suggest looking at message ordering
  - Ordering was suggested by Lily Liu [6]
  - Placeholder 4.2 in [2].


Remaining items from the top eleven;
------------------------------------
Pull-based notification                         14  DONE?
Preventing unwanted subscriptions               7
“Const” subscriptions                           7
Managing subscriptions as a group               7
Notification of subscription death              7


Matt Roberts
IBM WebSphere Messaging Design and Development
Hursley Park, England. +44 1962 815444
matt.roberts@uk.ibm.com
MP 211 / DE3H22

[1]
http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/11589/Durability_Proposal.doc
[2]
http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/15959/wsn-WS-NotificationPolicy-1.3-draft-01a.doc
[3]
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200410/msg00039.html
[4]
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200503/msg00022.html
[5]
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200501/msg00010.html
[6]
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200410/msg00038.html


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