- From: Massimo Paolucci <paolucci@icarus.cimds.ri.cmu.edu>
- Date: Thu, 3 Oct 2002 11:26:02 -0400
- To: Monika Solanki <monika@dmu.ac.uk>
- Cc: www-ws <www-ws@w3.org>
Monika, The profile model in daml-s describes services' capabilities. So it can describe both the capabilities of the providers (the advertisements) as well as what is expected by the requesters (the requests). If the requests are expressed in a format that is different from the advertisement, then of course there should be a translation somewhere. I can see only three places where this translation has to occur: 1. in the registry: the registry accepts requests in multiple formats, but then it reconciles the differences 2. in the requester: the requester may compile the request in some format, and then convert it to DAML-S 3. in the transport: this case assume the existance of intermediaries between the requester and the registry. These intermediaries may perform the translation. Few years back Joseph Giampapa and I implemented an agent called interoperator that performed similar translation to interface Retsina with OAA. --- Massimo
Received on Thursday, 3 October 2002 11:26:14 UTC