- From: <gerhecar@alumni.uv.es>
- Date: Wed, 7 Apr 2004 00:36:48 +0200 (CEST)
- To: public-sws-ig@w3.org
Hi My name is German, a student form Universidad de Valencia, and I'm going to write about matchmaking algorithm and the plugin/subsumes matching. I have some questions about this concepts which are mentioned in "Semantic Matching of web services" from Paolucci&all in 2002. I understand about plugin matching when the provider has a OutputA more general than the OutputR from requester, and this classes hasn't have a subclassOf relation. And the subsume relation is when the provider has a outputA more specific (or restricted) than the OutputR from requester, and no subclassOf relation between these classes. Is it ok?? For example, I have the next Ontology: Camera | ---------------- | | DigitalCamera DigitalCamera_and_Flash DigitalCamera is subclassOf Camera and have one restriction: R1 --> isDigitalCamera = Yes DigitalCamera --> Camera & R1 DigitalCamera_and_Flash is subclassOf Camera and have two restriction: R1 --> isDigitalCamera = Yes and R2--> hasFlash = Yes DigitalCamera_andFlash --> Camera & R1 & R2 If in my profilerequest I request a DigitalCamera_and_Flash, and I have 2 providers: Provider1 which offers Camera (more general) and Providers2 which offers DigitalCamera. If you read the matching algorithm from the text of Paloucci&cia, first it compare if OutputR == OutputP, then if OutputR subclassOf OutputA and the the plugin and subsume filter. The first filter in my example doesn't matching anything The second filter in my example matchs the provider1 because OutputR issubclassOf OutputA. the third filter matchs the provider2 because OutputA is more general (or minus restrictive) than OutputR. --> is it correct? Is this the plugin concept and the correct behaviour of a matchmaker? If it's correct, the third filter offers a better provider than second, because the provider2 offers a digitalcamera (near my request), and the provider1 provides a worst service (only offers camera). Why a better filter (second filter) offers worst providers than a plugin filter offers? Another question: if I define DigitalCamera with the sameclassAs DigitalCamera is sameClassAs Camera and have one restriction: R1 --> isDigitalCamera = Yes DigitalCamera <--> Camera & R1 When I use a reasoner (Fact,SeBOR in my case) , it puts DigitalCamera_and_Flash as subClassOf DigitalCamera and when i have the same providers and the same request, the filters only offers me the provider2 (digitalCamera) (because filter2 detects the subClassOf relation added by the reasoner) Is this behaviour correct?? Can anyone give me a example of subsume/plugin relations and how can I detect this relation?? Excuse my bad English. Regards
Received on Tuesday, 6 April 2004 18:37:34 UTC