RE: [wsn] Conf call agenda

["Vambenepe, William N" <vbp@hp.com>]

Addendum to the agenda:

I forgot to add a "possible new issues" section. From the mailing list,
I see two potential new issues, both raised by Lily:
- Message generation and accumulation styles [8]
- SubscriptionManager Interface in BrokeredNotification [9]

Any other new issue?

[8]
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200503/m
sg00000.html
[9]
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200503/m
sg00001.html

Regards,

William

-----Original Message-----
From: Vambenepe, William N 
Sent: Sunday, March 13, 2005 10:23 PM
To: wsn@lists.oasis-open.org
Subject: [wsn] Conf call agenda

Monday 3/14, 9-10:30AM Pacific time
Toll Free Access Number: 866-639-4730
Toll Access Number: 574-948-0377
Participant PIN: 4474535

* Roll call 

* Assign scribe: Latha?

* Approval of minutes from February 28 [1] 

* Status of open action items  

AI 11 . Use case: Box-carring? Martin & Anish [If no update on 3/14
call, William proposes that the group either drops this use case and
associated AI or reassigns it]

AI 18 - Peter to update clarification of wsrp:Dialect use. TC will then
consider whether it wishes to raise an issue to use a WSN equivalent

AI 20 - Sanjay to add an issue on "Defining the concept of "sending" a
notification" (and tie into it reliability of brokers)

AI 21 - David Hull to look at text dealing with delivering notifications
and suggest clarifications

AI 26 - Rick to go through policy use cases and identify baseline policy
behaviors (i.e. default behaviors when no explicit policies).

AI 42 - Peter/Tom Maguire: Ensure resolution of WSN4.3 removes wording
about dialects being XPath-like.

AI 44 - Glen: Propose wording of sentence to resolve WSN 4.9. The
sentence should say that it is possible to define a topic space with a
namespace of '', and should discuss why you might want to do this.

AI 50:  Martin to make proposal for subscription operation operation
returning two EPRs: one to manage subscriptions and one to pull
notifications. 

AI 53 - Sanjay: to include the proposal for WSN2.28 in the issue list.

AI 54 - Sanjay: to create a new issue on wsa:RelatesTo header uasge.

AI 55 - Sanjay: To close issue 4.18

AI 56 - Igor: Fix typos in WS-Topics as described in [2]

AI 57 - William to send email to open straw-poll from previous conf call
to more people (on proposal for 2.23 that was discussed during the call)

AI 58 - Sanjay: Move 2.20 to resolved

AI 59 - Sanjay: Move 2.30 (Partial Notification) to the policy section
with status open, but not approach agreed.

AI 60 - Sanjay: To close 2.30 and cross reference in the policy section.


AI 61 - Sanjay: Move 2.13 and 2.31 to WS-Topics

* Face to face logistics: Sanjay posed directions [3] and hotel
recommendations [4]. Any question?

* Issues left unfinished after previous call:

2.23: Is Subscription a WS Resource? Disposition of Steve's proposal [5]
and/or William's proposal from the previous call [6] (we left the issue
after straw poll in order to invite more people to participate in straw
poll).

* Issues not discussed during previous call:

* Review of other open issues outstanding against BaseN

    1.3 Security section needs more specific advice
    1.5 Term Event is not clearly defined
    1.6 Grouping of instances of a particular role
    2.6 Third party subscriber can be a security concern
    2.25 Indirection via WSRP and WSRL
    2.26 Targeting [specific set of] notification consumers

* Status of "approach agreed" issues outstanding against BaseN

    1.7 Indirect Notification pattern
    2.7 Updating resource properties
    2.13 Bindings for sending messages to Consumer
    2.17 Common set of Faults related to TopicExpressions
    2.24 Use of term implied resource pattern
    2.33 Message Ordering/interleaving
    2.34 Supply details on missing faults
    2.35 Refactor the WSDL/XSD split
    2.37 TopicExpression RP to have attribute extensibility
    2.38 Topics RP to be renamed as TopicExpression

* Continue discussion on Pull notification (issue 1.4)
    - One EPR or Two
    - Mailbox proposal [7]
    - What behaviour do you get by default, and what requires a policy
specification?
    - What do Pause/Resume mean, with respect to Pull?

References: 
[1]
http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/11608/WSN_
Minutes.txt
[2]
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200502/m
sg00035.html
[3]
http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/11594/Palo
%20Alto%20driving%20directions.pdf
[4]
http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/11593/Palo
Alto_Hotels.doc
[5]
http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/10189/issu
e%202.23.proposal.1.doc
[6]
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200503/m
sg00003.html
[7]
http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200502/m
sg00033.html