Posted by patrick_maue on January 30, 2011 under Deliverable | 
Link to the PDF file:
D4.2 – Model annotation components and guidelines
Executive Summary:
This document describes the methodology we propose to semantically annotate environmental models, as well as the components that have been developed to perform the annotation process. Domain ontologies are one of the key elements in this process, hence we added at the end of the deliverable a discussion about how to induce domain ontologies from text and streams. In order to apply the guidelines described here to a real use case, we created the ENVISION simple use case (see section 1). It consists of a service composition including different OGC Web services: a Sensor Observation Service (SOS), a Web Feature Service (WFS) and a Web Processing Service (WPS).
In the second section of the document we extend the semantic annotation concepts we introduced in Deliverable 4.1 by adding new services like the Web Coverage Service (WCS), and by giving more details about annotations for environmental models. For each described service, a generic approach is presented considering the various representations taking part in the process: the Capabilities document, the Procedure-Oriented Service Model (POSM), the Web Service Description Language (WSDL), and the application ontology representing the data model (RDF data model). The annotation examples created for the ENVISION simple use case are also described to close the section. Different software components are required to proceed with the annotations within the ENVISION infrastructure. This paper presents some new developments (e.g. Service Model Translator (SMT)), and tools based on previous implementations from the SWING project (e.g. Web OntoBridge).
In section 3, we explain how these components are integrated in the architecture and how to use them. In the fourth section we present ontology induction from text and streams along with the results of using it to induce domain ontologies. We introduce the OntoGen Tool which is used for semi- automatic ontology induction, and illustrate its applicability on the data relevant for Envision. We have shown potential usage of semi-automatic ontology creation from the domain specific data for the general Envision domain and for one of the Envision case studies.
Posted by patrick_maue on January 19, 2011 under Deliverable |
A new deliverable has been published on the ENVISION website.
Link to the PDF file:
D1.2 Environmental Services and Models – Scenarios and Pilots – Requirements specification
Executive Summary:
The ENVISION project develops an infrastructure for deploying semantic web services and environmental models to given communities. The objective of this document is to present the requirements specification for the pilot cases of the project and to describe relevant data sources. This document is therefore the basis for the validation of the ENVISION Portal capabilities from the user point of view. We start by introducing the context of the document (section 1) and then explain the methodology used to identify requirements in the perspective of the evaluation of the results (section 2). The requirements are described (section 3) focusing on the different viewpoints of the methodology. A resulting table is then presented (section 4) in order to formally summarize the requirements. At the end, section 5 concludes the document.
Posted by patrick_maue on January 17, 2011 under Deliverable |
Link to the Deliverable:
ENVISION Adaptive Execution Infrastructure Version 1 – Initial development and user guide
Executive Summary:
A core component of Envision is the Execution Infrastructure, which is responsible for supporting the execution of environmental service chains, their data-driven adaptation and the semantic-based mediation among the constituent services. These features constitute the operational core of Envision and will support the functionality of the Envision Portal.
The goal of this deliverable is to
- provide an overview of the features of the Envision Execution Infrastructure implemented in version 1.0 and
- provide a user-guide with details on the installation and use of the Infrastructure.
This document is based upon the deliverable D6.1 ENVISION Adaptive Execution Infrastructure – Architecture Specification, which provides details on the architecture and properties of each of the Execution Infrastructure components. Therefore, interested readers should refer to deliverable D6.1 for additional technical details. To facilitate its objectives, this document provides a short introduction to the Envision Execution Infrastructure and its features, which have been implemented in version 1.0. Next, we provide details on the installation process that should be followed and the set of users that are supported by this version of the infrastructure. We also provide descriptions of the steps that should be followed for the deployment and execution of an environmental service chain. Finally, we conclude with a short summary of the presented material and some preliminary remarks about the version 1.0 of the infrastructure.
Posted by patrick_maue on under Deliverable, Dissemination |
Link to the download:
MaaS Composition Portal Version 1 – Initial development and user guide
Executive Summary:
This deliverable reports on the first release of the ENVISION composition portal. We follow the recommendations of D3.1 that the ENVISION service composition language should be based on (a subset of) the Business Process Modelling Notation (BPMN) and that the ENVISION composition portal should adopt and extend the open source Oryx Web-based BPMN editor. The first release of the composition portal provides:
- implementations of Oryx extensions to support OGC-specific properties of BPMN tasks;
- transformation of BPMN compositions to executable BPEL processes and associated WSDL files; and
- deployment of an Oryx instance (together with the above mentioned extensions) on a server to be used within ENVISION.
This deliverable provides details on the aforementioned items and puts them in the context of the ENVISION overall architecture. In addition, this deliverable outlines the features planned for the next release of the composition portal.
