Figure 3 - uploaded by Oscar Díaz
Content may be subject to copyright.
Source publication
Portlets (i.e. multi-step, user-facing applications to be syndicated within a portal) are currently supported by most portal frameworks. However, there is not yet a definitive answer to portlet interoperation whereby data flows smoothly from one portlet to a neighbouring one. Both data-based and API-based approaches exhibit some drawbacks in either...
Context in source publication
Context 1
... portlet's ontology, bookFlightOnto, reflects this process as a collection of input and output OWL-S atomic process: return- FlightsAvailable_OS, departureFlightChoice_IS and the like. Fig- ure 3 shows an excerpt of this ontology where the suffix OS (output service) and IS (input service) denote output and input Atomic Pro- cesses, respectively 3 . ...
Similar publications
In the last decades, the increasing complexity of industrial information technology has led to the emergence of new trends in manufacturing. Factories are using multiple Internet of Things (IoT) platforms to harvest sensor information to improve production. Such a transformation contributes to efficiency growth and reduced production costs. To deal...
![Figure 1: EA Meta model for PEGS acc. to [32], [37]](profile/Ivan-Demydov-4/publication/355189941/figure/fig1/AS:1078584739397632@1634166049269/EA-Meta-model-for-PEGS-acc-to-32-37_Q320.jpg)
Enterprise Architecture (EA) frameworks provide a wide range of architecture components. Contextual EA components provide the necessary guidance to design specific architectures in a given context e.g. for PanEuropean Government Services (PEGS). Contextual EA components help to describe the background and scope of architecture work and provide a gr...
Many of the existing CAD systems do not properly address the residential electrical needs. In this specific market CAD system capabilities are often too complicated and beyond the scope. This project proposes and implements a much simpler CAD application that matches needs of electrical engineering drafters covering the residential and commercial l...
The fourth Industrial Revolution sets higher standards for the manufacturing itself and all associated processes. A promising direction in this context is the concept of Zero-Defect Manufacturing (ZDM) aiming at further automatization and optimisation of the production processes to reduce resources and avoid useless elements in the production chain...
access control is a key element when guaranteeing the security of online services. However, devices that make the Internet of Things have some special requirements that foster new approaches to access control mechanisms. Their low computing capabilities impose limitations that make traditional paradigms not directly applicable to sensors and actuat...
Citations
... Option U2 is facilitated by the trend towards offering open APIs that allow access to its underlying domain and event models. In [7] e.g., Diaz et al. describe a method that uses deep annotation, i.e., an ontology representation, to define the data flow from one portlet to another. Therefore, objects are related semantically on a data level. ...
Complex workflows require intelligent interactions. In this paper we attack the problem of combining user interfaces of specialized applications that support different aspects of objects in scientific/technical workflows with semantic technologies. We analyze the problem in terms of the (new) notion of full semantic transparency, i.e., the property of user interfaces to give full access to an underlying semantic object even beyond application lines. In a multi-application case full semantic transparency is difficult, but can be achieved by representing the semantic objects in a structured ontology and actively supporting the application-specific framings of an object in a semantic interface manager. We evaluate the proposed framework in a situation where aspects of technical constructions are distributed across a CAD system, a spreadsheet application, and a knowledge base.
... The approach described in [47] aims at using semantic web service descriptions for assembling portal applications from portlets. The work described in [48] and [49] shows how semantic annotation of contents delivered by portlets can be used to allow basic interactions between portlets. The work described in [50] shows how ontologies can help building mashup applications to integrate contents from diverse data sources in one mashup. ...
Integration of software applications can be achieved on different levels: the data level, the business logic level, and the user interface level. Integration on the user interface level means assembling the user interfaces of existing applications in a framework allowing seamless, unified interaction with those applications. While integration on the user interface level is desirable both from a software engineering as well as from a usability point of view, most current approaches require detailed knowledge of the integrated applications and make the implementation of a common interaction that involves different applications a difficult issue.In this paper, we propose a framework using ontologies for application integration on the user interface level by encapsulating the applications in plugins. Our approach is to use different ontologies for characterizing applications and the interactions possible with them, and for semantically annotating information objects exchanged between applications. Thus, the domain-independent and the domain-specific parts are untangled, which makes the framework applicable to different domains. An instance-based reasoner is used to process the ontologies and to compute the possible interactions, thus enabling integration at run-time.In an example from the domain of emergency management, we show how our approach helps implementing cross-application interactions more easily, thus significantly lowering the barriers for interoperability.
... While ontologies have been used to integrate applications on the database and business logic layer (Doan & Halevy, 2005;W3C, 2004, using ontologies for user interface integration is a new and widely unexplored field. Díaz, Iturrioz, and Irastorza (2005) discuss an approach which allows pre-filling form fields in different applications based on data from other applications. The input and output data are annotated by using ontologies defining the real world domain, and based on those annotations, data pipes between the different forms are defined. ...
Ontologies have been increasingly used in software systems in the past years. However, in many of those systems, the ontologies are hidden "under the hood". While a lot of useful applications of ontologies on the database and business logic layer have been proposed, the employment of ontologies in user interfaces has been gaining comparatively little attention so far. For providing a deeper understanding of that field as well as assisting developers of ontology-enhanced user interfaces, the authors give an overview of such applications and introduce a schema for characterizing the requirements of ontology-enhanced user interfaces. With this article, a state of the art survey of approaches is presented along with promising research directions.
... There have been examples for employing ontologies in portal and mashup development [2], which help showing related data in different applications at the same time. Another approach shows how data links can be established for automatic form-filling [7]. Unlike in the approach presented in this paper, these examples are restricted to data visualization and form-filling, i.e. no further cross-application interactions are possible. ...
There are different strategies to integrate software sys-tems: integration on the data layer, on the business logic layer, and on the user interface layer. The latter area, recently gaining attention by the rising popularity of Web 2.0 mashups, can benefit heavily from formal models and ontologies. In this paper, we argue why integration on the user interface level requires formal semantics. We present a framework using ontologies for user interface integration and discuss the relevant research tasks and links to related research fields.
... It rather focuses on communication between a portlet and its backend system than on inter-portlet communication and on user interaction. The work described in [13] uses ontologies to annotate the contents delivered by portlets. That approach is rather data-centric and has little focus on interaction. ...
Application integration can be carried out on three different levels: the data source level, the business logic level, and
the user interface level. With ontologies-based integration on the data source level dating back to the 1990s and semantic
web services for integrating on the business logic level coming of age, it is time for the next logical step: employing ontologies
for integration on the user interface level. Such an approach supports both the developer (in terms of reduced development
times) and the user (in terms of better usability) of integrated applications. In this paper, we introduce a framework employing
ontologies for integrating applications on the user interface level.
... The approach described in [8] uses semantic web services, i.e., web services described by means of ontologies for communication between a portlet and its backend system. The work described in [9] uses ontologies to annotate the contents delivered by portlets. The authors of [3] propose an approach of using ontologies for building mashup applications to integrate contents from diverse annotated data sources. ...
Modularization is almost the only feasible way of implementing large-scale applications. For user interfaces, interactions involving more than one module generate dependencies between modules. In this paper, we present a framework that uses ontologies for building UIs from independent, loosely coupled modules. In an example scenario, we show how that framework is used to build an application for emergency management.
... [RS05,SHP02,NBM07]). The automatic composition of presentation-layer components is considered in [DI05]. These approaches focus on either the matching and adaptation of complex arguments and protocols or the selection of services and links using semantic information. ...
... As we see, this is the most important contribution of that work and an aspect that we should consider to add in our statechart diagrams, in order to represent the information exchange between two portlets. In [4], we present our proposal to portlet aggregation, extending fragment markup of the portlet with semantic information. This set of data might be used by the designer of the portal to specify the mapping rules between the portlets she wants to pipe. ...
A portal is a key component of an enterprise integration strategy. It provides integration at the user interface level, whereas other integration tech- nologies support business process, functional or data integration. To this end, portlet syndication is the next wave following the successful use of content syn- dication in current portals. A portlet is a front-end application which is rendered within the portal framework. From this perspective, portlets can be regarded as Web components, and the portal as the component container where portlets are aggregated to provide higher order applications. Unlike back-end integration ap- proaches (e.g. workflow systems), portlet aggregation demands front-end solu- tions that permit users navigate freely among portlets in a hypertext way. To this end, the Hypermedia Model Based on Statecharts is used. This model uses the structure and execution semantics of statecharts to specify both the structural or- ganization and the browsing semantics of portlet aggregation. Besides familiarity, statecharts bring formal validation to portal design, helping portal designers in the development of structured portals. As a prove of concept, this model has been realized in the eXo portal platform.
... For the data-flow to be automatic, the portal should be able to understand what the fragments are about (i.e. the extended meta-data) and perform the mapping of that data among portlets. How this mapping is done has been previously presented at [6]. By contrast, this paper focuses on how the portlets' fragments are annotated. ...
Portlets are currently supported by most portal frameworks. However, there is not yet a deniti ve answer to portlet interoperation whereby data o ws smoothly from one portlet to a neighboring one. One of the approaches is to use deep annotation. By providing additional markup about the background services, deep annotation strives to interact with these underlying services rather than with the HTML surface that conveys the markup. In this way, the portlet can extend portlet markup with meta-data about the processes this markup conveys. Then, the portlet consumer (e.g. a portal) can use this meta-data to guide mapping from available data found in markup of portlet A to required data in markup of portlet B. This mapping is visualised as portlet B having its input form (or other ìin- putî widget) lled up. However, annotating is a cumbersome process that forces to keep in synchrony the meta-data and the resources being annotated (i.e. the markup). This paper presents an automatic process whereby annotations are gen- erated from portlet markups without user intervention. We detail our prototype using Lixto Visual Wrappers to extract semantic data from the markup.
... B. Cupid [48] ) zur (semi)automatischen Abbildung von einer Struktur auf eine Zielstruktur spielen dabei eine wesentliche Rolle. Architekturen zur Metasuche auf Webquellen, die sich hinter komplexen Formularen verstecken [32], oder die semantische Integration von Portlets [22] sind weitere Integrationsansätze , die eng mit Webdatenextraktion zusammenwirken. ...
Das World Wide Web kann als die größte uns bekannte „Datenbank“ angesehen werden. Leider ist das heutige Web großteils auf
die Präsentation für menschliche BenutzerInnen ausgelegt und besteht aus sehr heterogenen Datenbeständen. Überdies fehlen
im Web die Möglichkeiten Informationen strukturiert und aus verschiedenen Quellen aggregiert abzufragen. Das heutige Web ist
daher für die automatische maschinelle Verarbeitung nicht geeignet. Um Webdaten dennoch effektiv zu nutzen, wurden Sprachen,
Methoden und Werkzeuge zur Extraktion und Aggregation dieser Daten entwickelt. Dieser Artikel gibt einen Überblick und eine
Kategorisierung von verschiedenen Ansätzen zur Datenextraktion aus dem Web. Einige Beispielszenarien im B2B Datenaustausch,
im Business Intelligence Bereich und insbesondere die Generierung von Daten für Semantic Web Ontologien illustrieren die effektive
Nutzung dieser Technologien.
