[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsn] Groups - WSN conf call modified
I have just arrived in Tokyo after a long flight, and I don't think I'll be able to make this call. Dave -----Original Message----- From: peter_niblett@uk.ibm.com [mailto:peter_niblett@uk.ibm.com] Sent: Sunday, February 27, 2005 6:09 PM To: wsn@lists.oasis-open.org Subject: [wsn] Groups - WSN conf call modified WSN conf call has been modified by Mr Peter Niblett Date: Monday, 28 February 2005 Time: 09:00am - 10:30am 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 February 14 [1] * Status of open action items AI 11 . Use case: Boxcarring? Martin & Anish AI 14 - RickC/Lily to write a proposal for WSN2.28 (from Oct F2F). See [2] 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 22 - William to explore the possibility of saying something on using the wsa:RelatesTo header in the context of WS-Notification AI 26 - Rick to go through policy use cases and identify baseline policy behaviors (i.e. default behaviors when no explicit policies) AI 35 - Sanjay: Update WSN 4.22 to say that spec must describe what is the default if the attribute is not specified 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 47 - Fred: Explain what issue 4.18 means. See email from Fred [4] AI 50: [NEW] Martin to make proposal for subscription operation operation returning two EPRs: one to manage subscriptions and one to pull notifications. AI 51: [NEW] WS-BaseN editors to review conformance with issues 2.14 and 2.15 and report findings AI 52. [NEW] David Hull to produce mailbox-pull proposal. See[9] * Potential new issues? - Inconsistency in WS-Topics. See [5] * Review issue 2.23: Is Subscription a WS Resource? See [7] * 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 2.31 Namespace prefix change may result in unbound QNames Proposal to move to WS-Topics [6] 2.32 Dialect of TopicExpression in Subscribe MUST be specified. See [8] * Status of "approach agreed" issues outstanding against BaseN 1.7 Indirect Notification pattern 2.7 Updating resource properties 2.12 Resolving XML names in TopicExpression Proposal to move to WS-Topics [6] 2.13 Bindings for sending messages to Consumer 2.17 Common set of Faults related to TopicExpressions 2.20 QOS regarding change of subscription properties 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 [9] - 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/11409/2005 0214-wsn-minutes.doc [2] http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/11589/Dura bility_Proposal.doc [3] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200502/m sg00048.html [4] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200502/m sg00034.html [5] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200502/m sg00035.html [6] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200502/m sg00037.html [7] http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/10189/issu e%202.23.proposal.1.doc [8] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200502/m sg00041.html [9] http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200502/m sg00033.html Minutes: This event is one in a list of recurring events. Other event dates in this series: Monday, 14 February 2005, 09:00am to 10:30am PT Monday, 14 March 2005, 09:00am to 10:30am PT Monday, 28 March 2005, 09:00am to 10:30am PT Monday, 11 April 2005, 09:00am to 10:30am PT Monday, 25 April 2005, 09:00am to 10:30am PT Monday, 09 May 2005, 09:00am to 10:30am PT Monday, 23 May 2005, 09:00am to 10:30am PT Monday, 06 June 2005, 09:00am to 10:30am PT Monday, 20 June 2005, 09:00am to 10:30am PT Monday, 04 July 2005, 09:00am to 10:30am PT Monday, 18 July 2005, 09:00am to 10:30am PT Monday, 01 August 2005, 09:00am to 10:30am PT Monday, 15 August 2005, 09:00am to 10:30am PT Monday, 29 August 2005, 09:00am to 10:30am PT Monday, 12 September 2005, 09:00am to 10:30am PT Monday, 26 September 2005, 09:00am to 10:30am PT Monday, 10 October 2005, 09:00am to 10:30am PT Monday, 24 October 2005, 09:00am to 10:30am PT Monday, 07 November 2005, 09:00am to 10:30am PT Monday, 21 November 2005, 09:00am to 10:30am PT View event details: http://www.oasis-open.org/apps/org/workgroup/wsn/event.php?event_id=7106 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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]