This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9676 - Eventing: Introduce the concepts of event descriptions and NotificationWSDLs in section 9
Summary: Eventing: Introduce the concepts of event descriptions and NotificationWSDLs ...
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: externalComments, reviewerSatisfied
Depends on:
Blocks:
 
Reported: 2010-05-07 08:22 UTC by Antoine Mensch
Modified: 2010-07-28 09:10 UTC (History)
1 user (show)

See Also:

Attachments

Description Antoine Mensch 2010-05-07 08:22:52 UTC 
Currently, section 9 mentions NotificationWSDLs, but they are only introduced in Appendix A: introducing them at the beginning of section 9, and explaining that it is the type of metadata that is expected to go in the EventSource policy assertion would help.
Comment 1 Robert Freund 2010-05-11 22:47:34 UTC 
Add the following to the pseudo-schema
<!-- Notification WSDL can go here - see Appendix x.y -->
<!-- EventDescription Data can go here - see Appenfix x.y -->

add to definition of format name xs:any policy assertion
If the Event Source advertises Notification WSDL then it MUST appear as a child of the FormatName element. and do this for EVD data too.
Comment 2 Robert Freund 2010-05-12 16:23:05 UTC 
reviewer satisfied http://lists.w3.org/Archives/Public/public-ws-resource-access/2010May/0032.html