Data.ParliamentNic Gould – Parliamentary Digital Service

April 2015mail@nicgould.co.uk

Overview

• Open Data Platform for Parliamentary Data

• Standard data publishing APIs for internal systems

• Data can be shared internally or publically on the web

• General purpose base layer supporting any file based data

• Enhanced semantic layer provides added value:• RDF, GraphDB, ELDA (Linked Data API)

Architecture

Semantic Layer

• GraphDB store for all RDF data

• ELDA implementation of Linked Data API sits in front of SPARQL endpoint

• Apache server as reverse proxy cache for improved performance

• Custom ‘explore’ interface on top of ELDA for data discovery

• For each dataset:• Data modelled as RDF and aligned with existing data

• Published data converted to RDF and stored in GraphDB

• API endpoints configured using ELDA

Semantic Layer cont’d

• Benefits –• ELDA APIs are quick to set up and relatively flexible

• Data from APIs returned as simple JSON/XML/CSV – no RDF knowledge required

• Challenges –• Performance and stability

• Overcoming limitations of ELDA and RDF

• Availability of semantic skills

• Confidence and ‘buy in’ from senior stakeholders

Technologies

• Windows Servers, VMWare (Internal) and cloud based (External)

• SQL Server 2012 (core platform)

• .NET for custom developments

• CKAN for public facing website

• OWLIM SE 5.3

• ELDA by Epimorphics