Re: [wsdm] MEP Edits from todays Conference Call

[John DeCarlo <jdecarlo@mitre.org>]

Hello,

I don't know if I am interpreting this correctly, but let me quote a 
section of the Basic Profile 1.0 below.

Heather Kreger wrote:

> Hi folks,
> 
> Here is section 1.3 Message Exchange Patterns after todays discussion:
> 
> 1.1.1 Message Exchange Patterns
> [FR002] MUST support request-response style interaction between a manager
> and a manageable resource for interface. {#38}
>       [FR002.1] Must support Synchronous delivery of messages and
> request/response styles. {#142}
>       [FR002.2] Should support Asynchronous delivery of messages and
> request/response styles
> 
>       [FR002A] Should support asynchronous interactions between a manager
>       and a manageable resource for interface.
> 
> 
>       [FR002B] Should support one-way style interaction (asynchronously)
> 
> 
>          <check what WS-I supports/>
> 

"5.4.2 Allowed operations

Solicit-Response and Notification operations are not well defined by 
WSDL 1.1; furthermore, WSDL 1.1 does not define bindings for them.

R2303 A DESCRIPTION MUST NOT use Solicit-Response and Notification type 
operations in a wsdl:portType definition."

Request-Response seems to be the only type supported.


> 
> [FR003]  MUST support delivery of notifications from manageable resources
> to manager. (Source: IBM, HP, MPTC)
> 
> 
> 
> 
>       [FR003.1] The notification receiver SHOULD be able to control what
> notifications are sent to it. (filtering and/or subscription at managed
> resource side) (Source: HP)
>       [FR003.2] The notification receiver SHOULD be able to indicate
> whether it wants to receive notifications asynchronously as and when they
> happen or poll them periodically. (Source: HP) {#90}
>             [FR003.2C] SHOULD support asynchronous delivery of
> notifications
>             [FR003.2.D] MUST support synchronous polling for notifications
>             [FR003.2.E] The managed resource MUST be able to indicate if it
> supports asynch or polling notifications mechanisms.
>       [FR003.3] Must support guaranteed notifications. {#90} (and advertise
> its support)
>       [FR003.4] Must support ordering of notifications from a managed
> resource’s perspective. {#90}
>       [FR003.4] Support synchronous as well as asynchronous. {#142}
> <Delete: Dup of 3.2>
> 
> Please send additional requirments for a notification mechanism to the list
> before next week.
> 
> Heather Kreger
> STSM, Web Services Lead Architect for SWG Emerging Technologies
> Author of "Java and JMX: Building Manageable Systems"
> kreger@us.ibm.com
> 919-543-3211 (t/l 441)  cell:919-496-9572

-- 

John DeCarlo, The MITRE Corporation, My Views Are My Own
email:      jdecarlo@mitre.org
voice:      703-883-7116
fax:        703-883-3383
DISA cube:  703-882-0593