This article presents sparqlines: statistical observations fetched from SPARQL endpoints and displayed as inline-charts. An inline-chart, also known as a sparkline, is concise, and located where it is discussed in the text, complementing the supporting text without breaking the reader's flow. For example, the GDP per capita growth (annual %) [Canada] claimed by the World Bank Linked Dataspace. We demonstrate an implementation which allows scientists or authors to easily enhance their work with sparklines generated from their own or public statistical linked datasets. This article includes an active demonstration accessible at http://csarven.ca/sparqlines-sparql-to-sparkline.
In this article we introduce sparqlines, an integration of statistical data re‐ trieval using SPARQL with displaying observations in the form of word-size graphics: sparklines. We describe an implementation which is part of a Web based authoring tool (dokieli). We cover how the data is modelled and ex‐ posed in order to be suitable for embedding; demonstrate how to embed data as both static and dynamic sparklines and discuss the technical requirements of each; and walk through the user interactions to do so.
Our contribution is the generation of a well-established visual aid to reading statistical data (the sparkline) directly from the dataset itself, at the time of authoring the supporting text as part of the writing workflow. This enables authors who are already publishing data to use it directly, as well as encourag‐ ing them to make their data available for others to use, and offers an easy way to present the reader with a way to better understand the information.
We conclude with a discussion, including design considerations. The code of our implementation is open source, and we invite you to try it out and make requests for more advanced features: https://github.com/linkeddata/dokieli.
The earliest known implementation of an inline-chart was designed and pro‐
grammed by Peter Zelchenko and Mike Medved to represent historical charts
efficiently in the QuoteTracker software in early 1999 [
Sparkline graphics typically have a variable long dimension and a con‐ strained short dimension. In the case of a typographic line, the constraint can be fixed to the height of the font-size of the encapsulating component. For ex‐ ample, the computed CSS height value of the embed HTML element that contains the sparkline on the current viewing device is 20px, and so the em‐ bedded sparkline in this paragraph will have a vertical aspect ratio as such.
Sparklines appear in many places where small datafeeds are useful; pro‐
grammatical insertion in text-editors and spreadsheets, fitness feeds from
wearable watches, social media analytics, streaming real-time quotes, elec‐
troencephalograms, system dashboards and trays, temperature and stock ac‐
tivity, to name a few. Studies show that novice and experienced investors us‐
ing stock reports with Sparklines will experience reduced cognitive load [
Sparklines in line, bar, column or win/loss graphs can be programatically
included in Google Drive documents by including data from an embedded ta‐
ble or sequence of numbers via the Google Charts API [
The Wayback Machine uses sparklines to show an application of the snap‐ shots of a URL through time:
There are sparkline implementations in JavaScript libraries like d3.js and jQuery. Sparkline implementations also exist for command-line interfaces. These tools tend to take input data in tabular form (CSV). Sparklines can also be created by simple use of Unicode characters: ▂▁▄▃▆▅█▇.
Statistical data that is modelled with the RDF Data Cube vocabulary [
Sgvizler is a SPARQL result set visualisation JavaScript library that uses
Google Charts API to create sparkline images [
Investigation of analysis and visualisation of piracy reports have been con‐
ducted through endpoint querying with a SPARQL client for R [
CubeViz was developed to visualise multidimensional statistical data. It is a
faceted browser, which utilizes the RDF Data Cube vocabulary, with a chart
visualisation component [
Linked Statistical Data Analysis [
In order to use sparqlines, data has to be both well-formed and available over a SPARQL endpoint. Here we briefly discuss both of these requirements.
The RDF Data Cube vocabulary is used to describe multidimensional sta‐ tistical data. It makes it possible to represent significant amounts of heteroge‐ neous statistical data as Linked Data which can be discovered and identified in a uniform way. To qualify for consumption as a sparqline, the data must conform with some of the integrity constraints of the RDF Data Cube model, e.g., IC-1 (Unique DataSet), IC-11 (All dimensions required), IC-12 (No dupli‐ cate observations), IC-14 (All measures present).
Additional enrichments on the data cubes can improve their discovery and reuse. Examples include but not limited to; providing human-readable labels for the datasets (with language tags), classifications, and data structure defini‐ tion, as well as provenance level data like license, last updated.
In order to allow user interfaces which can utilise a group of observations in a dataset, slices should be made available in the data. This enables consuming applications to dissect datasets (through SPARQL queries) for arbitrary sub‐ sets of observations. For example, while it is possible to construct a general query to get all of the observations in a dataset which have a particular di‐ mension, it may be preferable to only query for such subsets provided that their structures can be identified and externally referenced. In the case of sparklines, one common use case for slices is to present data in time-series.
SPARQL queries are used to filter for graph patterns in the RDF Data Cube datasets. Depending on the user interface application, there may be mul‐ tiple queries made to the SPARQL endpoints in order to filter the data based on user input. For example, an initial query may be a cursory inspection to discover suitable datasets with given parameters, e.g., what the dataset is about, the type of dimensions and their values, and subsequent queries may be to retrieve the matching datasets or slices with observations and their measure values.
The data behind a sparqline can be static: a fixed historical set to which no new points are added; or dynamic: subject to change as new data is gathered. Both of these cases are accommodated by our implementation. Our implementation allows authors to select text they have written which de‐ scribes the data they want to visualise; it searches available datasets for those relevant to the text, and lets the user choose the most appropriate if there’s more than one. The sparqline is inserted along with a reference to the source.
A specific example workflow is demonstrated when this article is viewed in a Web browser (at its canonical URL: http://csarven.ca/sparqlines-sparqlto-sparkline). Enable the Edit mode from the ☰ menu and highlight the text GDP of Canada. What occurs is as follows: 1. User enters text in a sentence e.g., GDP of Canada. 2. User selects text GDP of Canada with their mouse or keyboard. 3. The user select the “sparkline” option from presented authoring toolbar. 4. The input text is split into two: 1) GDP and 2) Canada segments, whereby the first term is the concept, and the second is a reference area. Reference ar‐ eas are disambiguated against an internal dictionary. 5. System constructs a SPARQL query URL and sends it to the World Bank Linked Dataspace endpoint, looking for a graph pattern where the datasets of labels have “GDP” in them in which there is at least one observation for the reference area “Canada”. 6. User is given a list of datasets to select from which match the above crite‐ ria, and the user selects desired dataset. 7. System sends a SPARQL query to get the observations of the selected dataset for Canada. 8. A sparkline is created and displayed for the user, also indicating the number of observations it has. 9. If the user is happy with this visualisation they include it in the text. A hy‐ perlink to the dataset, and a sparkline SVG is inserted back into the sentence replacing GDP of Canada with GDP per capita growth (annual %).
Our implementation in dokieli automatically includes semantic annotations within the embedded sparqlines. The sparqline resource has its own URI that can be used for global referencing. The RDF statements are represented using the HTML+RDFa syntax, and they preserve the following information:
The part of the document to which the sparqline belongs (rel="schema:hasPart").
The human-readable name for the figure (based on the dataset used), where it was derived from (the qb:DataSet instance), and the generated SVG.
The SVG resource has statements to indicate: linked statistical dataset which was used (rel="prov:wasDerivedFrom"). human-readable name of the dataset (property="schema:name"). license for the generated SVG (rel="schema:license").
further information for each qb:Observation (rel="rdfs:seeAlso"). This information can be discovered and parsed as RDF, thus making easy to access and reuse by third-party applications. For example, another author can cite or include these sparqlines in their work.
We have presented a preliminary implementation of sparklines generated from SPARQL endpoints and embedded directly through authoring tool. This al‐ lows authors to visualise their data in an optimal way without breaking their workflow. However, there is a lot of scope for future work in this area. We now discuss some areas for further development.
Design principles: Tufte makes recommendations on readability, as well as
applying Cleveland’s analytical method of choosing aspect ratios banking to
45° [
Dataset interaction: Building on existing work in faceted searching and browsing of RDF data, authors can explore suitable datasets with a combina‐ tion of searching using natural-language and filtering through available datasets and dimensions of interest. This approach is convenient for datasets in RDF Data Cubes since they are highly structured and classified. Further work is needed to improve the process for disambiguation of the author’s input in natural language in order to discover appropriate URIs in the dataset.
Privacy considerations: Many researchers collect experimental data which has sensitive or identifiable information. This information should not be exposed through public SPARQL endpoints. Measures such as access control lists can allow researchers to generate sparqlines over sensitive data.
Data availability: SPARQL endpoints are notoriously unreliable and they may have high setup costs for new datasets. Applications which rely on end‐ points to generate sparqlines with dynamic data, may want to initially include a local cached copy from the last access point in the article. The application can then asynchronously fetch or subscribe for new updates.
The motivation and work on sparqlines was inspired by Edward Tufte’s educa‐ tion and popularisation of sparklines. Special thanks to Amy Guy and Ilaria Liccardi for their great support and tireless nagging to get this written up, as well as Jindřich Mynarz for help with SPARQL query optimisations.