Linked data/RDF/Semantic web
Notes from CurateCAMP SE 2012 breakout session
Emory has a linked data interest group:
- trains folks in basic SPARQL, sesame, SKOS
- email list
- pilot project will pull data out of silos and demonstrate potential (3 months)
RDF "readiness" cited as a first step.
OpenGraph (on Facebook) will make linked data more prevalent and personal.
Civil War regiments and SPARQL queries:
- what can a SPARQL query tell you that SOLR cannot?
- traversing relationships:
- combine parks service data on regiment movements with institutional archives data on soldier diaries.
- find indirect relationships between historical figures:
- shared a regiment
- in same battle
- served under same officer
- What should we (library and associated personnel) be doing to prep for linked data, semantic web, and RDF?
- What audiences would have the most to initially contribute?
- Where does the "same as" relationship sit?
- Where are the hubs?
- Who hosts?
- Who is "trustworthy"?
- Sesame (triple-store?)
- OpenRDF Workbench (built on Sesame)
- Linked Sailor (?)
- Zotero (as LOD-LAM project)
- FoF (Friend of Friend)
- Early RDF example
- Open Graph
- "Linked data is more about generic linking of data (forget RDF). Enabling graph of currently available data. RF is a way of serializing this data."
Obstacles to LD/SW/RDF implementation
- Developer time
- Narrow enough scope to manage a pilot
- Wide enough scope to be useful (large data)
- A challenge is demonstrating usefulness
- Have to ask questions that you can't ask of a faceting search engine.
- Difficult to present a "wow!" factor.
- Berners-Lee recommends assigned URIs.`