The QALL-ME Framework

User Manual

Table of Contents

1. Quick Tour: The QALL-ME Framework in 10 Points
2. Framework Description
2.1. Overview
2.1.1. Multilingual QA
2.1.2. Structured Answer Data Sources
2.1.3. Use of a Domain Ontology
2.1.4. Spatiotemporal Anchoring of Questions
2.1.5. Recognizing Textual Entailment for QA
2.1.6. Service Oriented Architecture
2.2. Prerequisites
2.2.1. Target Audience
2.2.2. Software Requirements
2.3. System Architecture
2.3.1. Question Answering Workflow
2.3.2. System Components
2.4. By the Way: What is QALL-ME?
3. Tutorials
3.1. Getting Ready for the QALL-ME Framework
3.1.1. Java EE 5 Application Server
3.1.2. Web Service Tester
3.1.3. Java Development Environment
3.1.4. Java Web Service API And Tools
3.1.5. Java EE 5 API
3.2. Getting Started with a First Demo
3.2.1. DemoKit Overview
3.2.2. Deploying a Web Service
3.2.3. Preparing for Web Services Testing
3.2.4. Initializing the QALL-ME Framework
3.2.5. Your First QA Run
3.3. Playing with the Demo Web Services
3.3.1. Being the QAPlanner
3.3.2. Using the Framework’s Components in Independent Java Applications
3.3.3. WS Invocations in the QueryGenerator
3.4. (Re-)Implementing Your Own QALL-ME Web Service
3.4.1. Introduction and Tutorial Preparation
3.4.2. Creating a WS Implementation Skeleton
3.4.3. Reading Resource Files
3.4.4. Finishing the Implementation
3.4.5. Deploying and Testing the New WS
4. Software Reference
4.1. Download Packages Overview
4.1.1. Stable Releases
4.1.2. Development Version Access
4.2. Framework Components Manual
4.2.1. General Remarks
4.2.2. System-Wide Components
4.2.3. Language Specific Components
4.2.4. Location Specific Components
4.3. Framework Tools Manual
4.4. Demo Components Description
4.4.1. General Remarks
4.4.2. Available Answer Data
5. Possible Extensions
A. Contact and Support
B. Acknowledgements
C. Legal Terms

List of Figures

2.1. Conceptual view on the QA workflow in the QA planner as a UMLUnified Modeling Language 2 activity diagram.
3.1. Running GlassFish application server.
3.2. Our freshly installed soapUI.
3.3. The GlassFish Web Applications administration page.
3.4. The GlassFish Deploy Enterprise Applications/Modules administration page filled in for the deployment of the WAR file of the LanguageIdentifier component.
3.5. The new Web Service page in GlassFish for the WAR file we have just deployed for the LanguageIdentifier.
3.6. The New soapUI Project dialog filled in with the LanguageIdentifier WS’s WSDL URL as the first WS description to import.
3.7. The soapUI workspace with the created projects and all the imported WS descriptions.
3.8. A complete SOAP request for the setTimex2SparqlConverter web method of the QueryGenerator is ready to be submitted.
3.9. The LanguageIdentifierPortBinding client window can be used to find out the WSDL target namespace of the LanguageIdentifier WS implementations.