Library of Congress will run Linked Data service
After forcing the closure of the lcsh.info service, which was set up by, Talking with Talis interviewee, Ed Summers to demonstrate how the Library of Congress Subject Headings could be represented as a Semantic Web application using SKOS [as I reported last month], there has been speculation as to when and what LC itself would do.
The following quote from a presentation [¹] at ALA Midwinter show that they have been thinking, and doing, something about it.
LCSH in SKOS. In 2008 the Library began a pilot to make a subset of LCSH freely available in SKOS format on the Internet. Making LCSH available in SKOS (Simple Knowledge Organization System) will facilitate its use for data manipulation and other applications on the Semantic Web and elsewhere. The web site on which it resided, lcsh.info, was not on an LC server, and was taken down in December 2008 to be replaced by the official site, expected to appear as <id.loc.gov/authorities> within the next couple of months. The Library of Congress remains committed to providing LCSH freely through SKOS. The former lcsh.info site will redirect users to the new URI.
A visit to id.loc.gov reveals the following [on a page last updated on January 22nd 2009]:
This site serves as a placeholder for forthcoming web services that will enable both humans and machines to programmatically access authority data at the Library of Congress. The initial services offered are influenced by — and therefore implement — the Linked Data movement’s approach of exposing and inter-connecting data on the Web via dereferenceable URIs. We aim to make resources available on this site within 6-8 weeks. Check this site regularly for more updates as we continue to develop this service!
and:
Initially, within 6 to 8 weeks, the Library of Congress will release its first offering: the Library of Congress Subject Headings. This will be an almost verbatim re-release of the system and content once found at the popular prototype lcsh.info service. The primary exception will be that the URIs for the data values will no longer take the form http://lcsh.info/{identifier}. Instead, they will start with http://id.loc.gov/authorities/{identifier}. If you have used the legacy lcsh.info metadata in an application, we advise updating to the new URIs, as we cannot guarantee a permanent redirect from old lcsh.info URIs to the new URIs at id.loc.gov.
Great to hear, and great for Ed. Both that his work has stimulated the LC in to action and also demonstrated how it should be done.
My only thought on this is why did they go through all the fuss and negative PR about taking down lcsh.info before the LC service that replaces it was up and running a couple of months later?
[¹] http://www.libraries.psu.edu/tas/jca/ccda/docs/lc0901.pdf (page 5)
Traffic Squad Police (LOC) image published in the The Library of Congress’ photostream on Flickr
Bowker, part of the
Following DS’s merger with the Axiell Library Group back in April 2008, they have made the unsurprising
Recent Comments