- From: David Martin <martin@AI.SRI.COM>
- Date: Tue, 15 Jun 2004 13:38:21 -0700
- To: Terry Payne <trp@ecs.soton.ac.uk>
- Cc: Daniel Elenius <daele@ida.liu.se>, public-sws-ig@w3.org
Terry Payne wrote: > > Daniel, > I am embarrassed to say that you are absolutely right. I was > convinced that this property was in OWL-S; but looking (briefly) at the > previous versions, I can't find it. hasProfile was removed from Process.owl, a while back, because we wanted to allow for the possibility / likelihood that a Process might have several different profiles, and to emphasize that, in general, the author of a process needn't know about or keep track of the profiles used to advertise the process. Of course having one or more instances of hasProfile would not preclude this possibility, but we felt that the use of hasProfile might be confusing (that is, it might imply to some users that the valid advertisement of a process is limited to the specified Profile(s). There was also a concern that it might create somewhat of a maintenance burden; that is, when and where would the hasProfile instances be maintained, for a given process? Finally, the information would be duplicative of relationships already captured elsewhere (in Service instances). > > This does raise some interesting questions: > > 1) profile:has_process > This is a functional property, pointing to a "Process". Should this be > functional, or may we want a profile to point to several processes (and > what would this mean)? We've always made the assumption that a profile is meant to represent a particular process. I think this simplifies some things, such as maintenance of the Profile in the face of process version changes. > > 2) inferring the profile given the process > If we have a full OWL-S model in some RDF store or reasoner, is it > possible to identify the profile given a reference to the process > model? Because of the "has_process" property, we can go the other way > round (and yes, this means we can do tricks with RDQL), but, for > example, could we generate the class of all profiles for a given set of > processes? This would be necessary if, for example, we wanted to know > the different non-functional parameters (attached to the profile) that > related to a given composition of processes? The "standard" answer is to look for all the Service instances that mention a given process, and then you can identify the related profiles because they are mentioned in the Service instances. The idea is that the Service instance bundles together a process with 0 or more profiles that the Service provider considers to be valid advertisements, and also with 1 or more groundings that the Service provider supports. We may well revisit these issues when it comes time to bring OWL-S up-to-date with WSDL 2.0. -- David > > Terry > > On 15 Jun 2004, at 08:13, Daniel Elenius wrote: > >> Regarding your figure: There is no hasProfile property in the >> current OWL-S. >> >> /Daniel >> >> Terry Payne wrote: >> This has my vote as well! >> >> I've attached a diagram that illustrates how processes, profiles and >> services are connected, and it is a bit of a tangled web... >> >> Terry >> >> >> >> >> >> <image.tiff> >> >> >> >> On 13 Jun 2004, at 16:57, Drew McDermott wrote: >> >> >> >> >> >> [David Martin] >> >> I'd like to collapse ProcessModel and Process, in Process.owl. I doubt >> if anyone will object to this, in principle, but I think it should be >> mentioned "for the record". It has been discussed, now and then, in >> the >> past. >> >> ProcessModel has always been a simple class which points to a Process >> and also to a "process control model". Of course, ProcessControlModel >> is just a placeholder; no one has ever done any work on it (that is, >> not >> in the context of OWL-S). (But note that I think there's some >> important >> work to be done in this area; it's just that it's not a near-term >> priority.) >> >> >> I never understood what a process-control model was supposed to be, so >> I agree with your proposal. >> >> -- Drew >> >> >> -- >> -- Drew McDermott >> Yale Computer Science Department >> >> >> >> >> _______________________________________________________________________ >> Terry R. Payne, PhD. | >> http://www.ecs.soton.ac.uk/~trp/index.html >> AgentLink III Co-coordinator | AgentLink III - >> http://www.agentlink.org >> University of Southampton | Voice: +44(0)23 8059 8343 [Fax: 8059 >> 2865] >> Southampton, SO17 1BJ, UK | Email: terry@acm.org / trp@ecs.soton.ac.uk >> >> >> >> >> >> -- >> Daniel Elenius >> Usable Ubiquitous Research Group (U2) >> Department of Computer and Information Science >> Linköping University, Sweden >> Tel: +46 13 28 56 06, Fax: +46 13 142 231 >> <mime-attachment> > > > _______________________________________________________________________ > Terry R. Payne, PhD. | http://www.ecs.soton.ac.uk/~trp/index.html > AgentLink III Co-coordinator | AgentLink III - http://www.agentlink.org > University of Southampton | Voice: +44(0)23 8059 8343 [Fax: 8059 2865] > Southampton, SO17 1BJ, UK | Email: terry@acm.org / trp@ecs.soton.ac.uk >
Received on Tuesday, 15 June 2004 16:36:45 UTC