Fork: 0
alex / chrome-lod

Extension for Chrome that checks pages as you browse for the presence of Linked Open Data behind them and reveals the underlying data.

Download ZIP 13 commits
Transfer to URL with SHA
latest commit fe97dcfc82
@Alex Tucker Alex Tucker authored on 16 Apr 2015
LICENSE.txt Applied MIT license. 9 years ago
README.md Applied MIT license. 9 years ago
background.js Applied MIT license. 9 years ago
codemirror-compressed.js Initial stab at a Chrome extension to reveal linked data. 10 years ago
codemirror.css Initial stab at a Chrome extension to reveal linked data. 10 years ago
contentscript.js Applied MIT license. 9 years ago
custom.css Applied MIT license. 9 years ago
fold.png Initial stab at a Chrome extension to reveal linked data. 10 years ago
fold.svg Check for Turtle as well as XML/RDF. Parse XML/RDF and look for licensing info. Click on revealed RDF to make it full height/width. Show traffic light icon depending on results of parsing. 10 years ago
jquery-ui.min.js Initial stab at a Chrome extension to reveal linked data. 10 years ago
jquery.min.js Initial stab at a Chrome extension to reveal linked data. 10 years ago
jquery.rdfquery.core.min-1.0.js Initial stab at a Chrome extension to reveal linked data. 10 years ago
jquery.rdfquery.rdfa-1.0.js Changed around the order of checks so that RDFa has a lower priority. Updated description and got rid of non-examples. Realized that rdfquery.rdfa includes rdfquery.core and so copied over kludges to rdfquery.rdfa. Slightly more forgiving of non-standard values of Content-Type. 9 years ago
manifest.json Applied MIT license. 9 years ago
package-icon-128.png Check for Turtle as well as XML/RDF. Parse XML/RDF and look for licensing info. Click on revealed RDF to make it full height/width. Show traffic light icon depending on results of parsing. 10 years ago
package-icon-16.png Check for Turtle as well as XML/RDF. Parse XML/RDF and look for licensing info. Click on revealed RDF to make it full height/width. Show traffic light icon depending on results of parsing. 10 years ago
package-icon-19.png Also look for redirects. 10 years ago
package-icon-48.png Check for Turtle as well as XML/RDF. Parse XML/RDF and look for licensing info. Click on revealed RDF to make it full height/width. Show traffic light icon depending on results of parsing. 10 years ago
package-icon.svg Check for Turtle as well as XML/RDF. Parse XML/RDF and look for licensing info. Click on revealed RDF to make it full height/width. Show traffic light icon depending on results of parsing. 10 years ago
pageIcon-amber.png Also look for redirects. 10 years ago
pageIcon-green.png Also look for redirects. 10 years ago
pageIcon-red.png Also look for redirects. 10 years ago
r-icon.png Initial stab at a Chrome extension to reveal linked data. 10 years ago
turn.css Initial stab at a Chrome extension to reveal linked data. 10 years ago
turn.js Initial stab at a Chrome extension to reveal linked data. 10 years ago
vkbeautify.0.99.00.beta.js Add RDFa parsing. 9 years ago
README.md

Chrome LOD extension

Author: Alex Tucker alex.tucker@bbc.co.uk

Copyright (c) 2015 BBC

Released under the MIT license (LICENSE.txt)

An extension for Chrome that looks for the presence of Linked Open Data behind the pages you browse and if available, reveals the underlying data.

Debugging/Building

In Chrome, open the tools/extensions page, ensure that developer mode is selected, and click to 'load unpacked extension...'. Select the directory you checked out the chrome-lod source to. This should enable the extension directly.

In order to package the extension for deployment, use the 'pack extension' button, which will result in a chrome-lod.crx file and associated keyfile.

Rationale

The extension runs once on each page you visit looking for any RDF data it can find in the following order:

1) Any tags in the page with relationship 'meta' or 'alternate' pointing to a URI with media-type application/rdf+xml, text/turtle or text/n3.

2) If the page you're visiting is the result of a redirect, then try to GET the previous page using content negotiation asking for an application/rdf+xml, text/turtle or text/n3 representation, following any further redirects.

3) Just use content negotiation on the current URI, again asking for RDF and following any redirects.

If an RDF representation is available, it will be rendered behind the current page and a peel-back animation will reveal the background RDF data as the mouse hovers over the top left corner of the page.

A limited check will be done to find out whether there is any machine readable license about the published RDF document.

Finally, a traffic light is rendered in the right of the omnibox to give an indication of conformance of the underlying linked (open) data.

Examples to try

http://sws.geonames.org/3020251/

http://data.nytimes.com/48675831753778135041

http://collection.britishmuseum.org/id/object/EOC3130

http://data.ordnancesurvey.co.uk/datasets/os-linked-data

http://id.loc.gov/vocabulary/organizations/ukmajru.html

http://beta.acropolis.org.uk/79a5f7dd9c284e1193e94797fbf2f90f

http://live.dbpedia.org/page/William_Shakespeare

http://data.europeana.eu/item/92056/BD9D5C6C6B02248F187238E9D7CC09EAF17BEA59

Todo

Parsing Turtle to look for licensing statements. Move to rdflib.js?

Checking that the license applies to the document URI of the RDF document.

Checking what license is being applied and that it is usable.