Using SPARQL – The Practitioners’ Viewpoint

Abstract

For guidance on citations see FAQs.

A Comparison of the Cognitive Difficulties Posed by SPARQL Query Constructs

“…They report that 71% of their respondents used property paths. Similarly to Bonifati et al [6], Warren and Mulholland [7] found that /, * and | were relatively frequently used operators. They also found that one or more (+) was relatively frequently used, and that ^ and ?…”

“…), disjunction (|), zero or more (*) and concatenation (/) were relatively frequently used. Complementing these studies, Warren and Mulholland [7] have surveyed the usage of SPARQL1.1 features. They report that 71% of their respondents used property paths.…”

Facade-X: An Opinionated Approach to SPARQL Anything

“…In addition, our approach leads to a more sustainable codebase. To give evidence of this statement, we use the tool cloc 20 to count the lines of Java code required to implement the core module of SPARQL Generate in Apache Jena (without considering format-specific extensions 21 ) and the RML implementation in Java 22 . SPARQL Generate and RML require developing and maintaining 12280 and 7951 lines of Java code, respectively.…”

“…Many SPARQL users fall into the category of end-user developer. In a survey of SPARQL users, [22] found that although 58% came from the computer science and IT domain, other SPARQL users came from non-IT areas, including social sciences and the humanities. Findings in this area [19] suggest that the data with which users work is more often primarily list-based and/or hierarchical rather than tabular.…”

Development of Intelligent SPARQL Query Editor

“…Однако набор поддерживаемых возможностей обычно значительно меньше, чем в SPARQL. Например, редактор RDF Explorer [4] поддерживает составление запросов, состоящих только из основного графового шаблона запроса 3 , где концепты могут быть заменены переменными. Авторы работы позиционируют RDF Explorer как редактор для пользователей, не являющихся экспертами.…”