what i wantfrom
Linked DataDan Chudnov dchud at umich edu 2008-02-23
code4lib 2009 preconf
part one
what i care about
i care aboutcontent
that *lasts*
i care aboutpersistence of precision
resilience of recall
i care abouteliminatingsoftware
i care aboutdoing web stuff
better
i don’t care aboutdata formats
i don’t care aboutthe LOD cloud
the “LOD cloud”
a“ready reference”
collection
the differenceis
Collection Development
data fordata’s sake
selected datafor a
designated community
one isn’t usefulthe other is antiquated
make this
useful
turn thisinto
linked data
part two
the obvious step
but first a disclaimer
MY OPINIONSDO NOT REFLECT
THOSE OF:MY EMPLOYERTHE US GOV’T
PRES. BARACK OBAMAMOST OTHER HOOSIERS
the obvious step
picture if you will
which, basically,was this
the webis made of links
but waitthere’s more
which, basically,was this
butnobody knows that
unless theyknow to look
so the obvious stepis
LINKTHISDATA
resource URI
rel=contents
rel=contents
rel=contents
(already has)resource URI
resource URI
resource URI
arrowsbecome
cross-reference
it becomescrawl-ablemine-able
integrated accessthrough
smart crawl/index
precision improveswith
rich metadataexplicitly linked
recall improveswith
explicit linksthrough authority recs
this isdoing web stuff
better
i care aboutdoing web stuff
better
just by doingHTML / HTTP
use URIs as names for thingsuse HTTP URIs
provide useful informationinclude links to other URIs
http://www.w3.org/DesignIssues/LinkedData.html
needs nonew software
i care abouteliminatingsoftware
part three
the not obvious step
two problemswith
the obvious step
1. there’s more stuff
2. stuff goes away
lcsh.info’s demise:
what did it break?
nothing
we’d only just startedthinking
what to do with it
what if we had?
what would have broken?
links.links would have
broken
we’re not hereto learn about
404’d data
if we applylinked data practices
to this
resource URI
rel=contents
rel=contents
rel=contents
(already has)resource URI
resource URI
resource URI
when an lcsh.infogoes away
all that breaks
same forall
of this
but notany
of this
a 404 webisn’t a better web
part four
what i thinkwe should work on
i care aboutcontent
that *lasts*
i care aboutpersistence of precision
resilience of recall
i wantlinked datathat lasts
*resilient*linked data
to-do #1cache linked data
if your site breakswhen links break
cache and link yourself
instead of this
do this
UChicagocache
same as
just likewe do
in ILS/OPACs
but, yknow,the better web way
so if this happens
your links still work
to-do #2proxy linked data
if this happens
your cache still work
but you can’trestart
dvcs lesson:no central server
is better
make every cacheits own
linked data source
instead of just this
UChicagocache
same as
enable this
UChicagocache
same as
same as
same as
same as
same as
if one goes downthe others live on
if others live onit’s all still linked
if it’s all still linkedwe can keep adding
so make your cached recs
useful linked URIs too
#1conventions for
caching linked data
#2conventions for
proxying linked data
food for thought
but now,let’s eat!