On Thu, Nov 12, 2009 at 10:02 PM, Ross Singer <rossfsinger_at_gmail.com> wrote:
> Rather than being an issue of credibility, I would say the biggest
> reason that id.loc.gov is getting relatively little use is because the
> communities that it's designed for aren't using it: libraries.
While we haven't really seen a great deal of people publishing RDF
data that use URIs from id.loc.gov yet, we are seeing a modest amount
of web1.0 users searching LCSH via the search form:
http://bit.ly/1MzHYc
That's just searches by people per day, not requests in general, or
bots. It's hard to imagine anyone other than library folks searching
LCSH. Granted, this isn't going to break any server request world
records. However it does show that there is some interest (increasing
if you squint right) in having LCSH available on the web, even in this
rudimentary form.
There have been a few little pockets of interest in using id.loc.gov
URIs in RDF. The W3C Semantic Web Use Cases documents, which use LCSH
to characterize the subject of their studies [1]. For example
http://www.w3.org/2001/sw/sweo/public/UseCases/NRK/
which is RDFa that can be translated to RDF/XML:
http://bit.ly/bTx93
I only heard about this because the editor for the Use Case documents
let me know via email. Which raises an interesting point: how are we
supposed to be able to track the use of our Linked Data resources? It
would seem that web server logs ought to be able to be used somehow
... but so far there doesn't seem to be an established pattern for
letting someone else know you are using their resources. It would be
neat to come up with some convention for letting a server know you are
binding to one of its URIs. Perhaps by doing a GET with the REFERER
set appropriately to the subject URI in the assertion.
//Ed
[1] http://www.w3.org/2001/sw/sweo/public/UseCases/
Received on Sun Nov 15 2009 - 22:01:33 EST