logo资料库

OWL-TC4-pDDL.操作手册-语义网资源.pdf

第1页 / 共15页
第2页 / 共15页
第3页 / 共15页
第4页 / 共15页
第5页 / 共15页
第6页 / 共15页
第7页 / 共15页
第8页 / 共15页
资料共15页,剩余部分请下载后查看
Introduction
Installation
Install XAMPP
Structure
Domains
Services
In the following example, precondition and effect formulas of the service bookpersoncreditcardaccount__service.owls, used for purchasing books online, are described.
Requests and Relevance sets
Used Ontologies
Disclaimer
Support and contact
Release history
OWL-S Service Retrieval Test Collection OWLS-TC Version 4.0 User Manual September 20th, 2010 Matthias Klusch, Mahboob Alam Khalid, Patrick Kapahnke, Benedikt Fries, Martin Vasileski Saarbrücken, Germany
Table of contents INTRODUCTION INSTALLATION INSTALL XAMPP STRUCTURE ..................................................................................................................................................................... 3 ...................................................................................................................................................................... 4 .................................................................................................................................................................... 4 ............................................................................................................................................................................ 6 ................................................................................................................................................................................. 6 ................................................................................................................................................................................ 6 ......................................................................................................................................... 11 ................................................................................................................................................................ 13 ......................................................................................................................................................................... 15 .................................................................................................................................................. 15 ............................................................................................................................................................. 15 DOMAINS SERVICES REQUESTS AND RELEVANCE SETS USED ONTOLOGIES DISCLAIMER SUPPORT AND CONTACT RELEASE HISTORY 2
Introduction This is the fourth version of the OWL-S service retrieval test collection named OWLS-TC4. The collection is intended to support the evaluation of the performance of OWL-S service matchmaking algorithms. It provides 1083 semantic Web services written in OWL-S 1.1 (and for backward compatibility OWLS 1.0) from nine different domains (education, medical care, food, travel, communication, economy, weapons, geography and simulation). It provides a set of 42 test queries which are associated with relevance sets to conduct performance evaluation experiments. Major improvements of OWLS-TC4 to former versions are the following: • Added 60 services and 10 queries in the geography domain, translated from SAWSDL to OWL-S 1.1 from Jena Geography Dataset 501 test collection • Added 16 services and 3 queries in the simulation domain, developed by DFKI for a project in simulated reality • 160 services and 18 queries contain Precondition and/or Effect as part of their services’ syntaxes are used for writing the process:AtomicProcess. PDDL 2.12 and SWRL3 condition expressions • Revising and editing the text descriptions of all services • Bug fixes Part of the services contained in OWLS-TC4 were retrieved from public IBM UDDI registries, and semi-automatically transformed from WSDL to OWL-S. Up to this version, around 30 people (DFKI, University of Jena, University of Thessaloniki and others) have worked on improvements and extensions. Relevance sets have been defined collaboratively. Please note that no standard test collection for OWL-S service retrieval does exist yet. As a consequence, OWLS-TC can only be considered as one possible starting point for any activity towards achieving such a standard collection by the community as a whole. OWLS-TC is available at semwebcentral.org: http://projects.semwebcentral.org/projects/owls- tc/ 1 Jena Geography Dataset collection, http://fusion.cs.uni-jena.de/professur/jgd/ 2 International Planning Competition, http://planning.cis.strath.ac.uk/competition/ 3 SWRL: A Semantic Web Rule Language, http://www.w3.org/Submission/SWRL/ 3
2. Copy the folders “services”, “ontology”, “queries” and “wsdl” of the OWLS-TC4 release to XAMPP (see following subsection “Install XAMPP”).4 the public http root folder (e.g. apache/htdocs) Installation 1. Install a local web server like the “Apache HTTP Webserver”: We recommend to install The usage of a local web server is necessary, since all ontologies used by a matchmaking tool, e.g. OWLS-MX, are expected to be available locally, and problems with incorrect paths to access ontologies used to describe service I/O concepts can thus be avoided. Install XAMPP Homepage: http://www.apachefriends.org/en/xampp.html Download: http://prdownloads.sourceforge.net/xampp/xampp-win32-1.5.0-pl1-installer.exe?download XAMPP is an easy to install Apache HTTP web server distribution also containing MySQL, PHP and Perl. Despite the fact that it contains more applications than needed for OWLS-TC it allows a first time user to avoid the difficult configuration of the Apache HTTP web server. The following manual should guide you through the process of installing XAMPP for the use with OWLS-TC, while using the above linked Windows version. 1. The installer starts with the language selection. Once you selected your desired language it will prompt you for an installation directory. You can select anything here, but we will consider the default “c:\apachefriends\xampp\” in this walkthrough. 2. The installation and configuration will take some minutes and temporarily open a command prompt. Once it is finished the installer will ask you if you want to install the web server as a windows service. Unless you want to start the local web server at windows startup you should deny this question. For the sole purpose of OWLS-TC the usual manual startup suffices. 3. Now you can start the Apache control panel, which will allow you to start the server by answering yes to the next question. 4. Using the control panel you can start the server by simply pressing the according Start” button next for the Apache. If you use Windows XP SP2 (or have any other firewall installed) your firewall will ask you if you if the program “Apache HTTP Server” should be blocked from the internet. It is necessary that you allow access to the program. 5. The installation of the web server is finished at this point. To install the test collection you can simply copy the directory “ontology”, “services”, “queries” and “wsdl” to the 4 The installer available from the Apache homepage in the Web, unfortunately, caused some problems with OWLS-MX on a WinXP Professional/Java1.5 equipped laptop. 4
apache web root directory (unless you specify something else it is “htdocs” in the XAMPP directory, so in our case “c:\apachefriends\xampp\htdocs”). 6. Now you can test if you can open the directory http://127.0.0.1/services/ in your web browser. The archive of the test collection contains the following subdirectories, All services of the test collection (subdirectories for the different supported OWLS- Versions). Supposed to be copied to the root directory of the local web server. - services - queries - ontology - domains All services requests of the test collection (subdirectories for the different supported OWLS-Versions). Supposed to be copied to the root directory of the local web server Ontologies used by the services and service requests. Supposed to be copied to the root directory of the local web server Contains all services sorted according to their domains - wsdl Contains the WSDL groundings for all of the services. Supposed to be copied to the root directory of the local web server 5
Structure Domains OWL-S Service Retrieval Test Collection version 4.0 consists of 10835 services from the following 9 domains: 1- education 2- medical care 3- food 4- travel 5- communication 6- economy 7- weapon 8- geography 9- simulation For information on the OWL-S web service description language standard of the W3C, please check, for example, http://www.daml.org/services/. indexed OWL-S DOMAIN #services #queries Services The current status of the number of services and queries related to each of these domains are as follows. 6 education 1 medical care 1 food 6 travel 2 communication 12 economy weapon 1 geography 60 10 simulation 16 3 The restrictions of OWL-S 1.1 service descriptions of this version of OWLS-TC are as follows: (a) The services are not describedby Process Model, but instead are directly describedby 286 73 34 197 59 395 40 Atomic process. (b) Grounding in WSDL is provided for all of the OWL-S 1.1 services. These WSDL groun- dings are created from the existing OWL-S services using the tool OWLS2WSDL6 . For each service, by using the option owls2wsdl from this tool, the WSDL file was created automatically 5 Some services appear in more than one category. Therefore the number of services is 1083 if just the first occurrence of each service is considered and 1140 if we consider repetitions accross different categories. 6 http://semwebcentral.org/projects/owls2wsdl/ 6
(although some manual changes had to be done, i.e. fixing the namespaces) and by using the option owl-s the groundings for the OWL-S services were created. The concepts used in the service input/output parts refer to ontologies (.owl files) that are stored in the /ontology directory. Preconditions and Effects In this version of OWLS-TC 160 Semantic Web Service descriptions, including 18 service requests, are extended with preconditions (logical formulas that must hold true in order for the service to be successfully executed) and effects (logical formulas which describe the results of the service execution over the state of the world). For describing the expressions of these preconditions and effects, PDDL 2.1 (Planning Domain Definition Language) syntax and SWRL (Semantic Web Rule Language) syntax is used. These expressions are written as part of the service’s process:AtomicProcess description. PDDL syntax offers more freedom for defining condition formulas offering wide range of logical operators, like conjunction, disjunction, atomic negation or quantified formulas. On contrary, SWRL syntax is more restricted and doesn’t support negation of whole atoms and disjunction of atoms. On the other hand this is not a major problem because by using rules of inference, disjunction and negation operators can be transformed in operators supported by SWRL. Classical negation of class predicates is supported in SWRL by using owl:complementOf The XML structure for describing preconditions and effects in PDDL is in the following format: Precondition Formula . Effect Formula 7
The precondition formulas follow this syntax: • • Atomic formula: (PREDICATE_NAME ?ARG1 ?ARG2 ... ?ARG_N) Conjunction of atomic formulas: (and ATOM1 ATOM2 ... ATOM_N) General conjunction: (and CONDITION_FORMULA1 ... CONDITION_FORMULA_N) • Disjunction of atomic formulas: (or ATOM1 ATOM2 ... ATOM_N) General disjunction: (or CONDITION_FORMULA1 ... CONDITION_FORMULA_N) • Negation of atomic formula: (not ATOMIC_FORMULA) General negation: • Quantified formula: (not CONDITION_FORMULA) (exists (?ARG1 ?ARG2 ...) CONDITION_FORMULA) And the effect formulas follow this syntax: • Added atom from service execution: • Deleted atom from service execution: • • Conjunction of atomic effects: (and ATOM1 ... ATOM_N) Conditional effect: (when CONDITION_FORMULA EFFECT_FORMULA) (PREDICATE_NAME ?ARG1 ... ?ARG_N) (not (PREDICATE_NAME ?ARG1 ... ?ARG_N)) All predicates and arguments are represented by their corresponding URIs, which point to specific classes or object properties described in ontologies. the the formulas of following example, precondition and effect service In bookpersoncreditcardaccount__service.owls, used for purchasing books online, are described. (and (http://127.0.0.1/ontology/ontosem.owl#Accepted ?http://127.0.0.1/services/1.1/bookpersoncreditcardaccount__service.owls#_CREDITCARDACCOUNT) (http://127.0.0.1/ontology/core-plus-office.owl#Authorized ?http://127.0.0.1/services/1.1/bookpersoncreditcardaccount__service.owls#_PERSON) (http://127.0.0.1/ontology/Mid-level-ontology.owl#accountHolder ?http://127.0.0.1/services/1.1/bookpersoncreditcardaccount__service.owls#_PERSON ?http://127.0.0.1/services/1.1/bookpersoncreditcardaccount__service.owls#_CREDITCARDACCOUNT)) As can be seen, the service precondition formula holds when the given user is authorized to use the service, it has been proven that the given credit card account belongs to her and her account is valid. The arguments _PERSON and _CREDITCARDACCOUNT are concepts which belong the predicates Accepted, Authorized and accountHolder are classes and object properties described by corresponding ontologies. the service’s input, and to 8
分享到:
收藏