Hybrid OWL-S Web Service Matchmaker

OWLS-MX is a hybrid semantic Web service matchmaker that retrieves services for a given query both written in OWL-S, and based on imported ontologies in the W3C recommended ontology web language OWL. For this purpose, the OWLS-MX matchmaker performs pure profile based service IO-matching but combines crisp logic-based semantic matching with syntactic token-based similarity metrics to obtain the best of both worlds - description logics and information retrieval. The "X" in OWLS-MX stands for five different instances (M0 to M4) of the generic hybrid matching scheme OWLS-MX depending on whether and which syntactic similarity metric is used. The OWLS-MX matchmaker is fully implemented in Java, uses the OWL-DL description logic reasoner Pellet for logic based filtering, and the cosine, loss-of-information, extended Jacquard, and Jensen-Shannon information divergence based similarity metrics for complementary approximate matching.
For your convenience, the matchmaker comes with an integrated graphical user interface which guides you through the complete process of matchmaking, including the building of your own test collection and individual performance test runs. For this purpose, we also developed a OWL-S service retrieval test collection youi may use (see below).

OWLS-MX has been developed at the German research center for artificial intelligence (DFKI) in 2005, as the first hybrid matchmaker available for  semantic Web services in OWL-S 1.0 and OWL-S 1.1.

For more detailed information on OWLS-MX, we refer to the Readme.txt and the selected publication:

• Klusch, M.; Fries, B.; Sycara, K. (2006): Automated Semantic Web Service Discovery with OWLS-MX. Proceedings of 5th International Conference on Autonomous Agents and Multi-Agent Systems (AAMAS), Hakodate, Japan, ACM Press. Best Paper Award Nominee.

You need Java J2SEE version 1.5 (JDK 5), or higher to run the OWLS-MX matchmaker: 
http://java.sun.com/j2se/1.5.0/download.jsp

For using OWLS-MX 1.1b, we refer the user to the documentation of its graphical user interface which is included in the distribution file.

• [RequestURI]     = [URI] URI to the OWL-S service request (the query). This input is mandatory.
• [ServicesPath]  = [String] Path to .owls files which includes all OWL-S services to register. Can either be a file URI or an actual path (will be converted to Java file type). This input is mandatory.
• [MatchingType]  = [int] refers to the OWLS-MX variant to be used. This input is mandatory
  
• 0 = OWLS-M0 = purely logic-based semantic matching
• 1 = OWLS-M1 = M0 + Loss-of-information similarity measure
• 2 = OWLS-M2 = M0 + Extended Jacquard similarity measure
• 3 = OWLS-M3 = M0 + Cosine similarity measure
• 4 = OWLS-M4 = M0 + Jensen-Shannon divergence based similarity measure
• [minDegree]     = [int] minimum degree of (hybrid) semantic match required
• 0 = exact
• 1 = plugin
• 2 = subsumes
• 3 = subsumed-by
• 5 = nearest-neigbour
• [minSim]     = [float] minimum degree of syntactic similarity required  (used for nearest-neighbour, or subsumed-by match). This value will be ignored when using OWLS-M0, and is 0.0 by default.
  

• Cyclic ontologies cause problems.
• Only adding of ancestor concepts allowed, not properties or domains of properties.
• Please note that checking the complete service retrieval test collection OWLS-TC v1 with associated ontologies by the matchmaker may take 3 hrs depending on your computing hardware, if you log the memory usage data.

• Benedikt Fries at  Develin@gmx.de

• Dr. Matthias Klusch at  klusch@dfki.de,  http://www.dfki.de/~klusch