On Thu, Nov 12, 2009 at 3:34 AM, Weinheimer Jim <j.weinheimer_at_aur.edu> wrote:
> I guess I don't understand what you are saying either. As my previous post tried to demonstrate, the id.loc.gov does *not provide* linked data.
The sole reason id.loc.gov/authorities exists is to provide linked
data. It's purpose is to provide /defreferenceable identifiers/ -
that it is all. The fact that there is an HTML view that is returned
at those locations is mere convenience (and they also provide the same
RDF, just realized through RDFa).
id.loc.gov/authorities is not inteded for you to link your webpage to
- it's not intended for direct human consumpution. It's for you
/data/ to link to. By knowing that we're all talking about the _same_
"Amharic language" (http://id.loc.gov/authorities/sh85004449#concept),
we can then build other assertions on that to relate /other kinds of
data/ to it and pull our subject headings /definitively/ into the web.
Here is the marc language code for Amharic as linked data:
http://purl.org/NET/marccodes/languages/amh#lang - so we can link
things written about Amharic and things written /in/ Amharic (note the
marccode resource links to id.loc.gov's concept). Because the marc
code resource links to lingvoj.org as well
(http://www.lingvoj.org/lang/am) a machine can also determine that
this is talking about the same thing as:
http://dbpedia.org/resource/Amharic_language
http://dbtune.org/musicbrainz/resource/language/zho
So now you can start drawing other resources that have to do with the
Amharic language.
Your link to www.biblio.tu-bs.de provides no capacity for you to bring
in any resources it relates to. In fact, if you look at the language
it uses "Try Worldcat", "Try Google Book Search" -- it is just taking
guesses that something will match on a string search. Those are
links, yes, but it's not linked data.
-Ross.
Received on Thu Nov 12 2009 - 10:16:23 EST