Issue: Additional Constraints required on EPRs

[David Snelling <d.snelling@fle.fujitsu.com>]

Folks,

This was posted to WSDM and relates to our refinement of EPRs for use in
WSRF. At our more abstract level of definition, we may not need as many
constraints as the WSDM people propose, but we might want some of these.

We should track them and see what their final choice is. This is the result
of their first discussion.

Bryan: You might want to split this into two issues.

> 
> 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.
-- 

Take care:

    Dr. David Snelling <d.snelling@fle.fujitsu.com>
    Fujitsu Laboratories of Europe
    Hayes Park Central
    Hayes End Road
    Hayes, Middlesex  UB4 8FE

    +44-208-606-4649 (Office)
    +44-208-606-4539 (Fax)
    +44-7768-807526  (Mobile)


This e-mail has been scanned by Trend InterScan Software.

This e-mail (and its attachment(s) if any) is intended for the named 
addressee(s) only. It may
contain information which is privileged and confidential within the 
meaning of the applicable law.
Unauthorised use, copying or disclosure is strictly prohibited and may 
be unlawful.

If you are not the intended recipient please delete this email and 
contact the sender via email return.

Fujitsu Laboratories of Europe Ltd (FLE) does not accept responsibility 
for changes made to this email after
it was sent. The views expressed in this email may not necessarily be 
the views held by FLE.

Unless expressly stated otherwise, this email does not form part of a 
legally binding contract
or agreement between the recipient and Fujitsu Laboratories of Europe Ltd (FLE).