- From: Asir Vedamuthu <asirveda@microsoft.com>
- Date: Thu, 11 Jun 2009 15:41:20 -0700
- To: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Here is a summary of draft requirements from the F2F minutes ... I. Developer of Event Sink generates code to dispatch and marshal Notifications using current WSDL tools a) raw notifications b) wrapped notifications c) Extension that impact on-the-wire messages (example, new formats) Non-functional requirement - make it easy II. Subscriber can see metadata about a set of potential Events (including schemas) that may be emitted by an event source Non-functional requirement - II 'screened' based on AuthZ III. A service designer can take metadata about a set of potential Event Types that may be emitted by an Event Source and implement the Event Source. IV. Realize ALL USECASCES without metadata V. Event Source can transmit multiple variations of Notifications (Raw, Wrapped, *) VI. Provide Subscriber with metadata that describes the variations of Notifications (eg supported formats) VII. A mechanism by which a subscriber can determine the WSDL based on how it subscribed to an event source Non-functional Requirement - all use case must have a 'reasonable' solution for constrained environments Non-functional requirement - limit inventions to application of well known technologies (such as WSDL, WS-Policy, MEX). Regards, Asir S Vedamuthu Microsoft Corporation
Received on Thursday, 11 June 2009 22:42:11 UTC