Groups - WSN Conf call modified

[peter_niblett@uk.ibm.com]

WSN Conf call has been modified by Mr Peter Niblett

Date:  Monday, 10 January 2005
Time:  10:00am - 11:00am PT

Event Description:
Toll Free Access Number: 866-639-4730
Toll Access Number: 574-948-0377
Participant PIN: 4474535

Agenda:
* Roll call 

* Assign scribe 

* Approval of minutes from November 22 2004 [1] 

* Notes from call on December 6 2004 

* Action items status  

 

AI 5 - WS-BrokeredNotif editors to insert a warning into spec that EPR usage subject to change pending WS-A WG achieving results (more clarity, last call, etc) (issue WSN2.14) [11/22 update: Still open, waiting on wording for BaseN (AI 4)] 

AI 7 - Editors to adopt for WSN2.15 the same resolution as WSRF did for their issue 30: WSA:action must match the SOAP uri 

AI 8 - WS-BaseNotif editors: WS-BaseNotification should have language that warns against changing subscription properties, 
and the outcome of changing them is very specific to the implementation (issue 2.20) 

- People to write use cases for the top policy statements that we decided to cover (from Oct F2F, policy discussion) 

AI 9 . Durability & Replay? Rick Cobb. See [8] 

AI 10 . Managing message rates? Igor 

AI 11 . Boxcarring? Martin & Anish 

AI 12 . Advertising continuity support: David H 

AI 13 - Steve: Create a detailed proposal for "pull-type" message retrieval (from Oct F2F, issue WSN1.4) 

AI 14 - RickC/Lily to write a proposal for WSN2.28 (from Oct F2F) 

AI 15 - Peter to write up proposal for issue WSN 4.2 (from Oct F2F) 

AI 16 - Peter and Igor to write proposal to add XPath 1 and XPath 2 as dialect 
(1st option in the list of options for issue WSN4.3 (from Oct F2F) 

AI 17 - DavidH, use case for "preventing unwanted subscriptions" 

AI 18 - Peter and Steve to write the clarification of wsrp:Dialect use. i.e. why this element is valuable and how 
is it applicable to the WSN uses. 

AI 19 - Sanjay to create new issue on use of wsrp:Dialect. See proposal [2] 

* Preparation for Face/Face
  
  - Logistics
  - Agenda


* Potential new issues? 

- Possible removal of yyyy/mm from URIs. See [4]

- Faults for Subscribe and GetCurrentMessage. See [9]

- DavidH's "snapshot and updates" proposal/ do we need getCurrentMessage? See [3] and related eMails 

- Do we need to say anything about execution order of filters? ([5] and follow-on "analysis of filtering" thread") 

* Issues discussion (if time allows)

- DavidH's proposal for issue 1.7 [6] 

- Double opt-in use case ([7] and follow-on thread) 



References: 
[1] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200411/msg00072.html 
[2] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200412/msg00011.html
[3] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200412/msg00016.html
[4] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200412/msg00040.html 
[5] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200411/msg00086.html 
[6] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200411/msg00071.html 
[7] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200411/msg00074.html 
[8] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200412/msg00032.html
[9] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200412/msg00028.html



Minutes:


View event details:
http://www.oasis-open.org/apps/org/workgroup/wsn/event.php?event_id=6723

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.