LOCAH Project and Considerations of Linked Data Approaches
Download as PPT, PDF3 likes1,064 views
The document discusses the LOCAH project, which focuses on exposing archival data as linked data to enhance data interconnection and accessibility on the web. It explains the concepts of linked data, URIs, and RDF, emphasizing the project's goals to create visualizations and address challenges in data modeling and licensing. Notable resources mentioned include Archives Hub, Copac, and examples of linked datasets relevant to the project.
More Related Content
Similar to LOCAH Project and Considerations of Linked Data Approaches (20)
More from Adrian Stevenson (20)
LOCAH Project and Considerations of Linked Data Approaches
- 1. UKOLN is supported by: LOCAH Project and Considerations of Linked Data Approaches 29 th March 2011 JISC Managing Research Data International Workshop, Birmingham, UK Adrian Stevenson LOCAH Project Manager
- 2. “ The term Linked Data refers to a set of best practices for publishing and connecting structured data on the Web.” “ the Semantic Web is the goal or end result… Linked Data provides the means to reach that goal” From ‘ Linked Data: The Story So Far ’ - Heath, Bizer and Berners-Lee 2009
- 3. The goal of Linked Data is to enable people to share structured data on the Web as easily as they can share documents today. Bizer/Cyganiak/Heath Linked Data Tutorial, linkeddata.org
- 4. In essence, it marks a shift in thinking from publishing data in human readable HTML documents to machine readable documents. That means that machines can do a little more of the thinking work for us. http://www.linkeddatatools.com/semantic-web-basics
- 5. But haven’t we been putting linked data on the web for years? In CSV , relational databases, XML etc? Well yes, but these approaches are not so easy to integrate Web 2.0 mashups work against a fixed set of data sources Linked Data applications operate on top of an unbound, global data space.
- 6. So what’s been happening?
- 8. Data.gov.uk Officially launched 21 st January 2010
- 9. BBC Music
- 10. A little bit of the techy stuff
- 11. Linked Data is … A way of publishing data on the web that: Encourages reuse Reduces redundancy Maximises inter-connectedness Enables network effects So how is this achieved?
- 12. Presentational tagging – HTML <h1>Manchester Physiotherapy Centre</h1> <p>Welcome to the Manchester Physiotherapy Centre home page. Do you feel pain? Have you had an injury? Let our staff take care of your body and soul.</p> <h2>Consultation hours</h2> Mon 11am - 7pm<br/> Tue 11am - 7pm<br/> Wed 3pm - 7pm<br/> Thu 11am - 7pm<br/> Fri 11am - 3pm <p> Please note that we will not be offering consultation during the weeks of the <a href=". . .">Olympic</a> games.</p>
- 13. Semantic tagging <company> <treatmentOffered>Physiotherapy</treatmentOffered> <companyName>Manchester Physiotherapy Centre</companyName> <staff> <therapist>Lisa Davenport</therapist> <therapist>Steve Matthews</therapist> <secretary>Kelly Townsend</secretary> </staff> </company>
- 14. Linked Data Design Issues URIs LD Design Issues Triples http://www.w3.org/DesignIssues/LinkedData.html
- 15. URIs and HTTP A ‘Uniform Resource Identifier’ (URI) provides a simple and extensible means for identifying a resource - RFC 3986 HTTP URIs can be ‘de-referenced’ A URL is a type of URI HTTP URIs are used for “real world” things http://adrianstevenson.com/id/me http://dbpedia.org/page/Tim_Berners-Lee
- 16. RDF Resource Description Framework a language for representing information about resources on the Web RDF can be used to represent things identified on the Web, even when they cannot be directly retrieved on the Web Describes relations using ‘triples’ http://www.w3.org/TR/REC-rdf-syntax/
- 17. Triples Triples statements ‘ Things’ have ‘properties’ with ‘values’ Subject – Predicate - Object Triples are the basis of RDF Archival Resource Repository Provides Access To The Rolling Stones Keith Richards Is Member Of
- 18. BBC Music
- 19. LOCAH Project
- 20. What is the LOCAH Project? L inked O pen C opac and A rchives H ub Funded by #JiscEXPO 2/10 ‘Expose’ call 1 year project. Started August 2010 http://blogs.ukoln.ac.uk/locah/ tag: #locah
- 21. What are the Archives Hub and Copac? National data services The Archives Hub is an aggregation of archival descriptions from archive repositories across the UK http://archiveshub.ac.uk Copac provides access to the merged library catalogues of libraries throughout the UK, including all national libraries http://copac.ac.uk
- 22. What is LOCAH Doing? Part 1: Exposing Archives Hub & Copac data as Linked Data Part 2: Creating a prototype visualisation Part 3: Reporting on opportunities and barriers
- 23. LOCAH Linked Data If something is identified, it can be linked to We can then take items from one dataset and link them to items from other datasets BBC VIAF DBPedia Archives Hub Copac GeoNames
- 24. BBC:Cranford VIAF:Dickens DBpedia: Gaskell Hub:Gaskell Copac:Cranford Geonames:Manchester DBpedia: Dickens Hub:Dickens The Linking benefits of Linked Data
- 25. Archives Hub Model (as at 14/2/2011) Archival Resource Finding Aid EAD Document Biographical History Agent Family Person Place Concept Genre Function Organisation maintainedBy/ maintains origination associatedWith accessProvidedBy/ providesAccessTo topic/ page hasPart/ partOf hasPart/ partOf encodedAs/ encodes Repository (Agent) Book Place topic/ page Language Level administeredBy/ administers hasBiogHist/ isBiogHistFor foaf:focus Is-a associatedWith level Is-a language Concept Scheme inScheme Object representedBy Postcode Unit Extent Creation Birth Death extent participates in Temporal Entity Temporal Entity at time at time product of in
- 26. Enhancing our data Already have some links: lexvo.org URIs for languages of archival materials reference.data.gov.uk URIs for time periods Postcodes, using both UK Postcodes URIs and Ordnance Survey URIs Virtual International Authority File Matches and links widely-used authority files - http://viaf.org/ DBPedia Also looking at: Library Congress Subject Headings
- 29. How are we creating the Visualisation Prototype? Based on researcher use cases Data queried from Sparql endpoint Use tools such as Simile, Many Eyes, Google Charts Also looking at custom built prototype
- 30. Use Case Slide http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_LOCAH
- 31. Visualisation Prototype Using Timemap – Googlemaps and Simile http://code.google.com/p/timemap / Early stages with this Will give location and ‘extent’ of archive. Will link through to Archives Hub
- 32. Some issues Data Modelling Sustainability Provenance Licensing
- 33. Data Modelling Challenges Archival description is hierarchical and multi-level Archives Hub: inconsistencies in data and lack of standardisation there's no content standard in the UK
- 34. Sustainability Can you rely on data sources long-term? Ed Summers at the Library of Congress created http://lcsh.info Linked Data interface for LOC subject headings People started using it
- 35. Library of Congress Subject Headings
- 36. Provenance Triples create individual statements OK if data ‘watermarked’ But can often be a problem
- 37. Licensing Nature of Linked Data: each triple as a piece of data ‘ Ownership’ of data Hard to track attribution We’re using CC BY-NC 2.0 for now
- 38. Questions?
- 39. Attribution and CC License Sections of this presentation adapted from materials created by other members of the LOCAH Project This presentation available under creative commons Non Commercial-Share Alike: http://creativecommons.org/licenses/by-nc/2.0/uk/
Editor's Notes
- #4: Has been described as a ‘data commons’, or more usually a Web of Data.
- #5: Problem for machines to extract meaning. At present, the raw data is not really available.
- #11: Data.gov.uk Newspaper
- #12: Principles underpinning the technology
- #13: Step back a bit to HTML HTML web of documents doesn’t encourage re-use, reduce redundancy. Are network effects but could be much better.
- #14: Note this is a considerable simplification of the detail in danger of misleading. Linked data exploits semantically meaningful tagging to encourage re-use, reduce redundancy etc.
- #15: http://www.w3.org/DesignIssues/LinkedData.html
- #17: Uses predicate logic. Goes back to Aristotle. Conceptualises things, and the relationships between things
- #22: Copac a union catalogue Both successful JISC services running for many years now Locah is a research project – will have to see if go into service with LD interface
- #24: In hypertext web sites it is considered generally rather bad etiquette not to link to related external material. The value of your own information is very much a function of what it links to, as well as the inherent value of the information within the web page. So it is also in the Semantic Web. Remember, this is about machines linking – machines need identifiers; humans generally know when something is a place or when it is a person. BBC + DBPedia + GeoNames + Archives Hub + Copac + VIAF = the Web as an exploratory space
- #25: You can imagine the research benefits if these principle were applied to datasets of your own interest area. British Library example. Improves Google visibility. Already seeing traffic via data.archiveshub.ac.uk
- #31: The aggregation and merging of the Hub data sources is enabled by the use of linked data. Linked data can also provide enrichment by linking to other data sources such as dbpedia.
- #34: “ lower level” units interpreted in context of the higher levels of description Arguably “incomplete” without the contextual data. Relations are asserted, e.g. member-of/component-of But there is no requirement or expectation that data consumers will follow the links describing the relations