Per discussion on the call.
D) Managed Resource Creation/Deletion Events. Manageability Consumer
is there first. As each resource is made manageable, an event
(containing the EPR in the payload) goes to the Consumer.
John DeCarlo wrote:
> Hello,
>
> Here is my take on this, to be shredded as needed.
>
> Use Case: Discover the WSDL to be used to manage one or more resources
> (don't have any EPRs as yet). However, to manage one specific resource,
> the EPR for that resource is needed.
>
> Options to solve the problem:
>
> A) Singleton Pattern Case. In the simple case of a singleton pattern
> (exactly one resource being managed), there is a convention for
> constructing a default EPR with null Resource Properties. This will
> allow the Consumer to go directly to manage the resource.
>
> B) Ask the Manageability Provider Case. Because the resources behind
> each of the Manageability Provider's Manageability Endpoint may be
> changing dynamically (e.g., running processes), WSDM defines a
> "GetListofResourceEPRs" operation that returns a list of all the resources.
>
> C) Ask the Registry Case. If all the EPRs for the managed resources are
> in a Registry, the Manageability Consumer should go there to search as
> needed, such as share the same manageability endpoint or the same WSDL.
>
> Vambenepe, William N wrote:
>
>> Here is the result of the discussion of these requirements at the conf
>> call today.
>>
>> Regards,
>>
>> William
>>
>>
>>
>> EPR->WSDL
>>
>> 1) Any EPR used to reference a WS-Resource must provide sufficient
>> information for the consumer to retrieve the WSDL description of the
>> WS-Resource.
>>
>> 2) The EPR must contain enough information to disambiguate which port
>> and/or service to use.
>>
>> 3) The WSDL component model of the WS-Resource must be complete (must
>> include, inline or import the schema of all referenced elements)
>>
>> WSDL->EPR
>>
>>> From the WSDL of a WS-Resource, there must be a way to retrieve the EPR
>>
>> of the WS-Resource. Some possible ways to do so:
>>
>> 1) Enough information to recreate the EPR is embedded in the WSDL.
>>
>> 2) There is enough information in the WSDL to invoke an operation to
>> retrieve the EPRs of the WS-Resources that share this WSDL description.
>>
>> 3) There is a well-know service such as a registry that can provide the
>> EPRs of the WS-Resources that share a given WSDL
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: Vambenepe, William N Sent: Tuesday, May 11, 2004 5:26 PM
>>> To: Wsdm (E-mail)
>>> Subject: [wsdm] WSRF requirements for discovery
>>>
>>>
>>>
>>> Hi all,
>>>
>>> To fulfill my action item from the conf call, here is proposed wording
>>> for two requirements to submit to the WSRF TC. They cover the first two
>>> points in the list of discovery features in my email from 4/21.
>>>
>>> Requirement 1:
>>>
>>> Any EPR used to reference a WS-Resource must allow the consumer to
>>> retrieve the WSDL description of the WS-Resource and deterministically
>>> disambiguate which port (of those in the WSDL) is to be used.
>>>
>>> Requirement 2:
>>>
>>> There must be a way for the consumer of the WSDL of a WS-Resource to
>>> know whether the WSDL contains enough information to access the
>>> WS-Resource. If not, there must be help in retrieving EPRs of
>>> WS-Resources that share this WSDL.
>>>
>>> Regards,
>>>
>>> William
>>>
>>> To unsubscribe from this mailing list (and be removed from the roster
>>> of the OASIS TC), go to
>>> http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leav
>>
>>
>> e_workgroup.php.
>>
>>
>> To unsubscribe from this mailing list (and be removed from the roster
>> of the OASIS TC), go to
>> http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.
>>
>>
>>
>
--
John DeCarlo, The MITRE Corporation, My Views Are My Own
email:
voice: 703-883-7116
fax: 703-883-3383
DISA cube: 703-882-0593
