WSN TC Meeting Minutes March 14, 2005
WSN TC meeting minutes – March 14, 2005
Scribe: Latha Srinivasan, HP
* Roll call
55 % present (Quorate)
* Approval of minutes from February 28 [1] : Approved w/o objections
* 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]
Martin: Some sort of a policy to be written up such as “single event per message”. Martin will write text for that.
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
Peter: Done on 27th Feb, 2005. Syntax and semantics based argument. Proposal: Raise an issue to investigate this further.
AI 20 - Sanjay to add an issue on "Defining the concept of "sending" a notification" (and tie into it reliability of brokers)
Sanjay: Done – Issue 2.39.
AI 21 - David Hull to look at text dealing with delivering notifications and suggest clarifications
David: Will suggest a general approach. Email posted on Friday March 11, 2005. Tied to issue 2.39.
AI 26 - Rick to go through policy use cases and identify baseline policy behaviors (i.e. default behaviors when no explicit policies).
Still open – will be done over the next 2 weeks.
AI 42 - Peter/Tom Maguire: Ensure resolution of WSN4.3 removes wording about dialects being XPath-like.
Still open.
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.
Still open.
AI 50: Martin to make proposal for subscription operation operation returning two EPRs: one to manage subscriptions and one to pull notifications.
Martin: Inclined to stick with Steve’s original proposal. Closed -- No Action.
AI 53 - Sanjay: to include the proposal for WSN2.28 in the issue list.
Done. Added a link to Rick’s posting on WSN mailing list.
AI 54 - Sanjay: to create a new issue on wsa:RelatesTo header uasge.
Done. Issue 2.14
AI 55 - Sanjay: To close issue 4.18
Done.
AI 56 - Igor: Fix typos in WS-Topics as described in [2]
Still open.
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)
Done.
AI 58 - Sanjay: Move 2.20 to resolved
Done.
AI 59 - Sanjay: Move 2.30 (Partial Notification) to the policy section with status open, but not approach agreed.
Done.
AI 60 - Sanjay: To close 2.30 and cross reference in the policy section.
Done.
AI 61 - Sanjay: Move 2.13 and 2.31 to WS-Topics
Done.
* Face to face logistics: Sanjay posted directions [3] and hotel recommendations [4]. Any question?
Sanjay will provide contact info before the F2F. Please send questions to Sanjay. Ballot to gauge attendance will be set-up by William.
* 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).
Steve G: Will remove opposition to suggestion. Open at the moment. Steve will work on the proposal.
* Issues not discussed during previous call:
* Review of other open issues outstanding against BaseN
1.3 Security section needs more specific advice
Raised against WS-Notifications whitepaper that was a submission document to the TC. Steve and David Hull will look at the whitepaper and work on what needs to be done. This is not an issue against WS-BaseN. Overall: Look at the whitepaper and see what needs to be moved in. Proposal: Close 1.3 and raise a new issue to say that “BaseN needs a section on Security”. Editors also look into what else needs to be moved in from whitepaper to their respective documents.
1.5 Term Event is not clearly defined
Three potential approaches:
1. Expunge all references to Event
2. Include a definition for Event.
3. Put the words to explain what it means in the context.
The only place we reference seems to be in the Non-Goals section in WS-BaseN. Resolution: expunge all references to “Event”.
Status: Open?
1.6 Grouping of instances of a particular role
Sanjay will look into this – and decide whether it is an impediment to achieving committee draft on WS-BaseN by next call.
The rest of the issues were not discussed during today’s call.
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
Editors: Go through this list and identify items that can’t be acted upon – finish this by next call on March 28 ’05.
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?
* New Issues since last call:
- Message generation and accumulation styles [8]
Three possibilities for producer to produce messages. Proposal: Move the text from description of “Resume” to description of “Pause”. Action: Raise an issue to do this.
- SubscriptionManager Interface in BrokeredNotification [9]
BrokeredNotification – NotificationBroker seems to have the responsibilities of SubscriptionManager in the “Requirements” section. However, the definition of interfaces later on does not discuss extending SubscriptionManager in NotificationBroker. This needs to be tightened up. Steve G: The text in requirements is not meant to imply this. No immediate benefits to mixing in the two portTypes. Proposal: Raise an issue to clarify the requirements section to be less ambiguous. Clarify the wording to say “NotificationBroker” does not need to mix-in SubscriptionManager. Sanjay: Related issue.. Should we split NotificationBroker and NotificationConsumer, Publisher interfaces? Spend some time at the F2F on brokers. Sanjay will raise an issue on the Issues list.
Any other new issue?
DurableNotification called out some policy assertions.. is there a syntax for saying that?
Next call: March 28 – public holiday in UK, Canada, Ireland and Spring Break week in the US. William will post a ballot for attendance.
[8]
sg00000.html
[9]
sg00001.html
References:
[1]
Minutes.txt
[2]
sg00035.html
[3]
%20Alto%20driving%20directions.pdf
[4]
Alto_Hotels.doc
[5]
e%202.23.proposal.1.doc
[6]
sg00003.html
[7]
sg00033.html