Mapping languages analysis of comparative characteristics

RDF generation processes are becoming more interoperable, reusable, and maintainable due to the increased usage of mapping languages: languages used to describe how to generate an RDF graph from (semi-)structured data. This gives rise to new mapping languages, each with different characteristics. However, it is not clear which mapping language is fit for a given task. Thus, a comparative framework is needed. In this paper, we investigate a set of mapping languages that inhibit complementary characteristics, and present an initial set of comparative characteristics based on requirements as put forward by the reference works of those mapping languages. Initial investigation found 9 broad characteristics, classified in 3 categories. To further formalize and complete the set of characteristics, further investigation is needed, requiring a joint effort of the community

On the Mental Workload Assessment of Uplift Mapping Representations in Linked Data

Self-reporting procedures have been largely employed in literature to measure the mental workload experienced by users when executing a specific task. This research proposes the adoption of these mental workload assessment techniques to the task of creating uplift mappings in Linked Data. A user study has been performed to compare the mental workload of “manually” creating such mappings, using a formal mapping language and a text editor, to the use of a visual representation, based on the block metaphor, that generate these mappings. Two subjective mental workload instruments, namely the NASA Task Load Index and the Workload Profile, were applied in this study. Preliminary results show the reliability of these instruments in measuring the perceived mental workload for the task of creating uplift mappings. Results also indicate that participants using the visual representation achieved smaller and more consistent scores of mental workload

Extending R2RML-F to support dynamic datatype and language tags

Linked data is often generated from raw data with the help of mapping languages. Complex data transformation is one of the essential parts while uplifting data which either can be implemented as custom solutions or separated from the mapping process. In this paper, we propose an approach of separating complex data transformations from the mapping process that can still be reusable across the systems. In the proposed method, complex data transformations include the entailment of (i) language tag and (ii) datatype present at the data source. The proposed method also includes inferring missing datatype information. We extended R2RML-F to handle data transformations. The results showed that transformation functions could be used to create typed literals dynamically. Our approach is validated on the test cases specified by the RDF mapping language (RML). The proposed method considers data in the form of JSON, thus making the system interoperable and reusable

Value-driven partner search for <i>Energy from Waste</i> projects

Energy from Waste (EfW) projects require complex value chains to operate effectively. To identify business partners, plant operators need to network with organisations whose strategic objectives are aligned with their own. Supplier organisations need to work out where they fit in the value chain. Our aim is to support people in identifying potential business partners, based on their organisation’s interpretation of value. Value for an organisation should reflect its strategy and may be interpreted using key priorities and KPIs (key performance indicators). KPIs may comprise any or all of knowledge, operational, economic, social and convenience indicators. This paper presents an ontology for modelling and prioritising connections within the business environment, and in the process provides means for defining value and mapping these to corresponding KPIs. The ontology is used to guide the design of a visual representation of the environment to aid partner search

A tribute to George Plafker

In a long and distinguished career, George Plafker has made fundamental advances in understanding of megathrust tectonics, tsunami generation, paleoseismology, crustal neotectonics, and Alaskan geology, all by means of geological field observations. George discovered that giant earthquakes result from tens of meters of seismic slip on subduction thrusts, and he did this before the theory of plate tectonics had become a paradigm. The discovery was founded on George's comprehensive mapping of land-level changes in the aftermath of the 1964 earthquake in Alaska, and on his similar mapping in the region of the 1960 earthquakes in Chile. The mapping showed paired, parallel belts of coseismic uplift largely offshore and coseismic subsidence mostly onshore -- a pattern now familiar as the initial condition assumed in computer simulations of subduction-zone tsunamis. George recognized, moreover, that splay faulting can play a major role in tsunami generation, and he also distinguished carefully between tectonic and landslide sources for the multiple tsunamis that accounted for nearly all the fatalities associated with the 1964 Alaska earthquake. George's classic monographs on the 1964 earthquake include findings about subduction-zone paleoseismology that he soon extended to include stratigraphic evidence for cyclic vertical deformation at the Copper River delta, as well as recurrent uplift evidenced by flights of marine terraces at Middleton Island. As a geologist of earthquakes, George also clarified the tectonics and hazards of crustal faulting in Alaska, California, and overseas. All the while, George was mapping bedrock geology in Alaska, where he contributed importantly to today's understanding of of how terranes were accreted and modified

rust-code-analysis: A Rust library to analyze and extract maintainability information from source codes

The literature proposes many software metrics for evaluating the source code non-functional properties, such as its complexity and maintainability. The literature also proposes several tools to compute those properties on source codes developed with many different software languages. However, the Rust language emergence has not been paired by the community’s effort in developing parsers and tools able to compute metrics for the Rust source code. Also, metrics tools often fall short in providing immediate means of comparing maintainability metrics between different algorithms or coding languages. We hence introduce rust-code-analysis, a Rust library that allows the extraction of a set of eleven maintainability metrics for ten different languages, including Rust. rust-code-analysis, through the Abstract Syntax Tree (AST) of a source file, allows the inspection of the code structure, analyzing source code metrics at different levels of granularity, and finding code syntax errors before compiling time. The tool also offers a command-line interface that allows exporting the results in different formats. The possibility of analyzing source codes written in different programming languages enables simple and systematic comparisons between the metrics produced from different empirical and large-scale analysis sources