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=20
> Sent: Tuesday, May 11, 2004 5:26 PM
> To: Wsdm (E-mail)
> Subject: [wsdm] WSRF requirements for discovery
>=20
>=20
>=20
> Hi all,
>=20
> 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=20
> first two
> points in the list of discovery features in my email from 4/21.
>=20
> Requirement 1:
>=20
> 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.
>=20
> Requirement 2:
>=20
> 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.
>=20
> Regards,
>=20
> William
>=20
> To unsubscribe from this mailing list (and be removed from=20
> the roster of the OASIS TC), go to=20
> http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leav
e_workgroup.php.
