WS Notification Teleconference
June 6th, 200512PM-1PM ET
Roll call
See website
Approval of minutes from F2F [1] [2] [3] [4]
Any objections? No objections, approved
Status of open action items
AI 56 - Sid/Igor: Fix typos in WS-Topics as described in [5]
[Peter] Leave open
AI 74 - BaseN editors to correct problems in implementation of issue 2.34 as described in [6]
[Bryan] not sure how 2.34 is resolved
[Peter] leave open
AI 76 - BaseN editors to update spec to tighten semantics of send/deliver (issue 2.39) - Needs verification
[Bryan] DaveH has tightened up semantics not verified
[Peter] close
AI 79 - Lily to propose new issue and solution outside BaseN to replace 2.26
[Peter] leave open
AI 81 - Chairs to recruit editors for the primer
[Peter] leave open (from F2F)
AI 82 - Spec editors to incorporate content from the white paper as described in [7]
[Peter] happened for BaseN; probably not for BrokeredN; leave open for Brokered and Topics
AI 85 - WS-Topics editors to respond to questions raised in Kato-san's email [8] regarding use of terms TopicPath, TopicExpression
TopicPathExpression, and the names of the related Faults.
[Peter] same state as AI56; leave open
AI 93 – WS-Topics editors: Edits/improvements to WS-Topics raised by Ian Springer. [9]
[Peter] same state as AI56; leave open
AI 94 – Sanjay to mark WSN 2.23 as Approach Agreed. See [10]
[Sanjay] done
AI 95 – Sanjay to mark WSN 2.36 as Approach Agreed. See [10]
[Sanjay] done
AI 96 - Chairs to create calendar entry for september F2F
[Peter] todo; leave open
AI 97 - Editors to update the status text in all specs. See process doc [11]
[Peter] NOT SURE ABOUT THIS ONE
AI 98 - Topics and BrokeredN 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. [12]
[Peter] done
AI 99 - Editors to move to new format for namespace URIs
[Peter] Done for BaseN not others
AI 100 - Peter to update process document with new namespace format URI. See [11]
[Peter] done; uploaded
AI 101 - Sanjay to check on soap action in absence of ws-a action.
[Sanjay] we should be ok; close
AI 102 - Sanjay to raise various new approach-agreed issues. See [10]
[Sanjay] done
- Action URI for faults in BaseN (2.48)
- Action URI for faults in BrokeredN (3.11)
- Disallow silent faults in BaseN (2.49)
- Disallow silent faults in BrokeredN (3.12)
- Make BaseN (examples) independent of SOAP level (2.50)
- Make BrokeredN (examples) independent of SOAP level (3.13)
- Simplify non-normative examples in BaseN (2.50)
- Simplify non-normative examples in BrokeredN (3.13)
- BaseN, remove references to specs that aren't in standards orgs (2.55)
- BrokeredN, remove references to specs that aren't in standards orgs (3.19)
- Topics, remove references to specs that aren't in standards orgs (4.25)
- Flexible placing of notification metadata (2.51)
- TopicExpressionDialects to be singular + minOccurs=0 (2.52)
- BaseN, change TopicPathExpression to be TopicExpression (2.53)
- BrokeredN, change TopicPathExpression to be TopicExpression (3.14)
- fIX BrokeredN subscribe to be consistent with BaseN (3.16)
- Fix namespace prefixes in BrokeredN (3.17)
- change BrokeredN TopicExpression RP to be TopicExpression (3.18)
- BaseN, use WS-Resource's ResourceUnknownFault (2.54)
- BrokeredN, use WS-Resource's ResourceUnknownFault (3.15)
- Bespoke method to destroy PublicationRegistration (3.20)
AI 103 - Chairs to send list of acknowledgements and ask if people want to be added/removed.
[Peter] leave open, to do
AI 104 - Chairs to produce list of reviewers for CDs
[Peter] skeleton document has been posted. Need volunteers
AI 105 - Chairs to schedule 1 hour meeting on June 13th.
[Peter] done
AI 106 - BaseN editors to delete Version f line 522 sentence "element MUST accept all NotificationMessages "
[Peter] not completed; leave open
AI 107 - BaseN editors to remove MUST from beginning of 5.2 PauseSubscription
[Peter] close
AI 108 - BaseN editors to change start of 4.2 from "will result in the creation" to "MUST result in the creation"
[Peter] close
AI 109 - Bryan to clarify new para "The NP MUST respond with ..." in the description of wsnt:Filter/wsnt:TopicExpression/@Dialect. This entire description of the component needs to be more clear.
[Bryan] not completed; leave open
* Status of BaseN - draft i [13] - deadline for CD approval is July 1st
[Peter] has everything but Pull-type notification; need verifications of issues; can we have a draft j with 1.4 by next week?
[Bryan] we can try
[Peter] comments back by next week based on draft i.
Issues actioned since Draft e
1.4 - Support for Pull-type notification
1.5 f Term “Event” is not clearly defined
2.1 h Topics are not optional in WS-BaseNotification
2.6 g Third party subscriber can be a security concern
2.23 i Is subscription a WS-Resource?
2.25 i Indirection via WSRF-RP and WSRL
2.32 f Dialect of TopicExpression in Subscribe MUST be specified
2.33 h Message ordering/interleaving
2.34 ? Additional Fault definitions
[Bryan] done by draft f
2.36 g Specify baseline Policy behaviour
2.39 f Tighten up semantics of send/deliver
2.41 i Use of wsrf-rp:Dialect
2.43 f Message generation and accumulation styles
2.45 f Typing of Notification payload – xs:any vs xs:anyType
2.46 i Should UseNotify be a policy utterance?
2.47 i Open content on messages
2.48 h Define action URI for fault messages and update the spec text to use wsa:Action
2.49 g Define faults exhaustively (no silent faults)
2.50 g Update non-normative examples
2.51 h Flexible placing of metadata
2.52 h TopicExpressionDialects to be singular (line 334 in version 1f)
2.53 g Use TopicExpression instead of TopicPathExpression
2.54 g Use WS-Resource defined ResourceUnknownFaultType
2.55 i Remove references to specs that aren't in standards orgs
AI76 ? correct problems in implementation of issue 2.34
[Peter] was this done?
[Peter] verification process should catch
AI82 i incorporate content from the white paper
AI97 i update the status text
AI99 i move to new format for namespace URIs
AI103 - Appendix A acknowledgements
AI106 - delete Version f line 522 sentence "element MUST accept all NotificationMessages "
[Peter] no evidence of this being done; resolution was to delete this sentence
AI107 i remove MUST from beginning of 5.2 PauseSubscription
AI108 i change start of 4.2 from "will result in the creation" to "MUST result in the creation"
AI109
Resolved prior to draft f
1.7 Indirect Notification pattern
2.3 Duration for the initial termination time is not allowed
2.7 Updating resource properties
2.11 Consumer can not identify the subscription causing notifications
2.13 Bindings for sending messages to Consumer
2.14 Is EPR the right construct?
2.15 Reliance on WS-Addressing
2.17 Common set of Faults related to TopicExpressions
2.18 WS-BaseNotification should allow any garbage collection mechanism
2.19 Soften the wording for the Subscribe operation
2.20 QOS regarding change of subscription properties
2.21 NotificationProducer resource property declarations
2.22 Pause/Resume message types
2.24 Use of term “implied resource pattern”
2.29 SubscribeResponse to specify effective termination time
2.35 XML schema separated from the WSDL file
2.37 TopicExpression RP to have attribute extensibility
2.38 Topics RP to be renamed TopicExpression
Questions arising, see [14], [15]
i) Extent of topic separation (2.1)
[Peter] DaveH was concerned about. Worried that separation of Topics was not as extensive as he had hoped. It should be possible to implement a Producer that did not use Topics at all. DaveH wanted to go further.
AI [Peter] Since DaveH is not on call email back to DaveH
ii) Cardinality of useRaw (2.46)
[Peter] Schema allows multiple useRaw (both ‘true’ and ‘false’ possible). Normative text says you MUST not do this and if you do it will fault. Should we have some schema way of expressing this?
AI [Peter] leave as is. Email to DaveH
iii) Review chapter 2 (terminology and concepts)
[Peter] as result of Whitepaper merge need to review all of the changes.
[Peter] volunteers to read through chapter 2 (Tom and Peter to mark up)
[Bryan] need non-editors
AI(Peter, Tom, Bryan) review, suggest alternatives via emails
iv) Review chapter 6 (Security considerations)
[Peter] review of chapter 6 as well. Volunteers?
[Peter] 6.2 needs work
AI Editors to copy 6.1 from WSRF CD specifications
[Tom] Treat as part of issue verification
AI Peter AI82 needs to be added to verification list above
v) Precise Spelling of Document ID + location URLs for the other specs
[Peter] version of process document that did not specify document ID and location URLs. Need to agree on references and URLS. Camel lower, camel mix or lowercase.
AIPeter Move to same style as format. Update process document with correct references.
vi) Reference to the (non-existent) Primer
[Peter] reference in section 7 to WS-Notification primer. CD time will not have primer available. Suggestion delete sentence referring to primer.
AI Editors remove sentence referring to WS-Notification primer.
* Assignment of issues to reviewers
[Peter]
AI Peter non-editors, assigned for issue resolution and email posted
* Update on WS-Brokered Notification and WS-Topics
[Peter] what is the current status
[Lily] half through text for issues; sometime this week
[Peter] If we can get to the same position for WS-Brokered for next week that we are with BaseN that would be good.
References:
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]
[9]
[10]
[11]
[12]
[13]
[14]
[15]