[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsn] Agenda for 6/27
Regrets -- tied up with JavaOne activities! I think I have completed my AI from last week's conf-call. Here is a summary of the relevant changes to the issues document (http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/13165/WSN _IssuesList2.12.doc) Updated WSN2.1: Topics are not optional in WS-BaseNotification Added WSN2.56: Schema validation error for fault types extended from WSRF BaseFaultType WSN3.21: Schema validation error for fault types extended from WSRF BaseFaultType WSN3.22: BrokeredNotification portType to include the PullPoint factory operation Thanks, Sanjay Patil SAP Labs - Palo Alto >-----Original Message----- >From: Vambenepe, William N [mailto:vbp@hp.com] >Sent: Friday, Jun 24, 2005 17:47 PM >To: wsn@lists.oasis-open.org >Subject: [wsn] Agenda for 6/27 > > >Date: Monday, 27 June 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 20 June [1] > unclear decision on 2.25 and 2.48 which were discussed based on >reviewer comments > >* Status of open action items > > >AI 56 - Sid/Igor: Fix typos in WS-Topics as described in [2] > >AI 79 - Lily to propose new issue and solution outside BaseN to replace >2.26 > >AI 81 - Chairs to recruit editors for the primer > >AI 82 - WS-Topics editors to incorporate content from the >white paper as >described in [3] > >AI 85 - WS-Topics editors to respond to questions raised in Kato-san's >email [4] regarding use of terms TopicPath, TopicExpression > TopicPathExpression, and the names of the related Faults. > >AI 93 WS-Topics editors: Edits/improvements to WS-Topics raised by Ian >Springer. [5] > >AI 97 - Editors to update the status text in all specs. See process doc >[6] > >AI 98 - WS-Topics editors to add sentence on precedence of document and >schema> Use text found in the BaseN draft > emailed to the list by David Hull on 05/19/05. [7] > >AI 99 - WS-Topics Editors to move to new format for namespace URIs > >AI 116 - Sanjay: Update resolution of 2.1 to including making >FixedTopicSet optional with default of true. >(is this done? Minutes say "Sanjay agreed". Does it mean the AI is >closed?) > >* Possible new issues > >* Status of BaseN - draft j [9] - deadline for CD approval is July 1st > >Issues that have been verified as ok > >2.32 Dialect of TopicExpression in Subscribe MUST be specified (2 >reviewers) >2.36 Specify baseline Policy behaviour (2 reviewers) >2.45 Typing of Notification payload xs:any vs xs:anyType (2 >reviewers) >2.49 Define faults exhaustively (no silent faults) >2.51 Flexible placing of metadata >2.53 Use TopicExpression instead of TopicPathExpression (2 reviewers) >2.54 Use WS-Resource defined ResourceUnknownFaultType > >Issues that have been checked - questions/rework arising >2.23 Is subscription a WS-Resource? >2.25 Indirection via WSRF-RP and WSRL >2.33 Message ordering/interleaving >2.34 Additional Fault definitions >2.39 Tighten up semantics of send/deliver >2.41 Use of wsrf-rp:Dialect >2.47 Open content on messages >2.48 Define action URI for fault messages and update the spec text to >use wsa:Action >2.50 Update non-normative examples >2.52 TopicExpressionDialects to be singular (line 334 in version 1f) >AI82 incorporate content from the white paper >AI97 update the status text > >Issues still to be verified > >1.4 Support for Pull-type notification >1.5 Term Event is not clearly defined >2.1 Topics are not optional in WS-BaseNotification >2.6 Third party subscriber can be a security concern >2.43 Message generation and accumulation styles >2.46 Should UseNotify be a policy utterance? >2.55 Remove references to specs that aren't in standards orgs >AI106 delete Version f line 522 sentence "element MUST accept all >NotificationMessages " >AI108 change start of 4.2 from "will result in the creation" to "MUST >result in the creation" >AI109 New paragraph "the NP MUST respond with..." > >* Update on WS-Brokered Notification (draft f) [10] and WS-Topics > >Issues that have been verified as ok >3.4, 3.6, 3.8, 3.11 (2 verifiers), 3.14, 3.16 (2 verifiers), 3.20 > >Issues that have been checked - questions/rework arising >3.10, 3.13, AI82 > >Issues still to be verified >3.1, 3.5, 3.7, 3.9, 3.10, 3.12, 3.15, 3.17, 3.18, 3.19 > > > > >References: >[1] >http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/1 3162/2005 >0620_WSNMinutes.html > > >[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/email/archives /200503/m >sg00031.html >[4] >http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives /200504/m >sg00018.html >[5] >http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives /200504/m >sg00035.html >[6] >http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/1 2795/Curr >ent%20WSN%20TC%20%20Process.htm >[7] >http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives /200505/m >sg00031.html >[8] >http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives /200506/m >sg00061.html >[9] >http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/1 3024/wsn- >WS-BaseNotification-1.3-draft-01j.doc >[10]http://www.oasis-open.org/apps/org/workgroup/wsn/download.p hp/13106/ >wsn-WS-BrokeredNotification-1.3-draft-01f.doc >[11] >http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives /200506/m >sg00048.html >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]