The State of Linked Government Data
by Richard Cyganiak on Aug 20, 2010
- 4,815 views
There are high expectations for Linked Government Data—the practice of publishing public sector information on the Web using Linked Data formats. This slideset reviews some of the ongoing work in the...
There are high expectations for Linked Government Data—the practice of publishing public sector information on the Web using Linked Data formats. This slideset reviews some of the ongoing work in the US, UK, and within W3C, as well as activities within my institute (DERI, National University of Ireland, Galway).
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Microsoft PowerPoint
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 20
- Downloads
- 98
- Comments
- 7
- Embed Views
- Views on SlideShare
- 4,815
- Total Views
- 4,815
Links:
1. http://groups.google.com/group/uk-government-data-developers/browse_thread/thread/6cebb03699ab87dc -- RDF archive release post from Leigh Dodds . 1 year ago Reply
BTW - did you actually look at the data.gov.uk mailing list thread re. this issue of RDF dumps (again nothing to do with a specific RDF format) to get some background to my gripe before drawling conclusions about my comments?
Links:
1. http://bit.ly/bnp1Xy -- data.gov.uk mailing list thread re. issue of LOD and RDF dumps (note: the responses I’ve received to date) . 1 year ago Reply
Look, you know I don’t have a preferred format for anything when it comes to structured linked data. That isn’t my point. Also, my comments have nothing to do with undermining the good work. My gripe (an one I will not let up on) is this: at the onset of LOD (remember the SWEO project) we agreed the following best practices for 'open data' published as 'linked data':
1. Produce an RDF dump
2. Load into SPARQL compliant RDF Store
3. Publish Linked Data (via whatever platform does the job for you)
4. Link to other Datasets in the Linked Data Cloud.
Also recall, we established that crawlers shouldn’t go pounding public SPARQL endpoints (since this ultimately disrupts other users), hence point #1.
If you take some time to research the history of this gripe of mine (see the data.gov.uk mailing list), I am sure you will find the responses I’ve received so far quite intriguing.
I hope I’ve made my point crystal clear?
Please do remember, we do not exist in an 'all or nothing' realm (at least I don’t). When I raise concerns about practices that ultimately lead to confusion, the gut reaction simply cannot be: You Don’t Like This etc.. I am raising a very serious point here.
How come Data.Gov have no problem producing RDF dumps (again nothing to do with a specific format, its RDF data in the format they have chosen). 1 year ago Reply
Nice presentation.
Only quibble: data.gov.uk ratings don’t reflect the fact that they do not offer actual RDF dumps. data.gov doesn’t have this issue and as a result anyone can load data.gov’s RDF datasets into RDF stores of their choice. In the case of data.gov.uk, the data is locked behind SPARQL endpoints.
Early LOD principle was: always accompany LOD data behind a SPARQL endpoint with an RDF archive so that user agents don’t pound SPARQL endpoints via crawling etc.. 1 year ago Reply