For talk given at code4lib north, Hamilton, Ontario, 2011-05-06. The video in slide 48 doesn't work here. To view it, visit http://www.youtube.com/watch?v=e-uwPje6XKg#t=6m34s and watch for one minute. The embedded version was included for emphatic educational purposes only.

1. WWIC?
linked library data
as a
customer service medium
@dchud - code4lib north - hamilton, on - 2011-05-06

2. Why Wasn’t I Consulted?
aka ‘WWIC’ - by Paul Ford

3. WWIC ==
the web is for
sharing opinions

4. Linked Library Data
aka ‘LLD’

5. LLD ==
the web is for
sharing data

6. sh w
t
a ra
th
ar eb is
d fo
g s
e
in
in i
r b
d ?
te
a e
g
l
h
su
s w
Linked LibraryoData
n
o
e
C
p
h
I
t
sn’t in
Wa io
y fo
n
h r
s
W

7. WWIC => the web *isn’t*
•a radio
• a tv
• a newspaper
• an encyclopedia
• a librarian

8. WWIC => the web *is*
a way
to
share
opinions and expertise

9. thoughtful platforms
for
opinions and expertise

10. if you’re building
a website,
ask yourself

11. “How can people
use it
to share
their
opinions and expertise
about my stuff?”

12. WWIC
http://www.ftrain.com/wwic.html

13. LLD
linked library data

14. use URIs as names for things
use HTTP URIs
provide useful information
include links to other URIs
http://www.w3.org/DesignIssues/LinkedData.html

15. an example
of
what we used to build

17. an example
of
what we we build now

18. Rembrandt at
artic.edu
authority record at OCLC

20. who’s linking
to my stuff
in wikipedia?

21. Rembrandt in linkypedia

22. Rembrandt from linkypedia

23. Picasso: name variants, search links

24. Picasso from more than linkypedia

25. platform for
following your nose
to cool stuff

26. lovely, but

27. WWIC?

28. if we stop here
we’re missing something

29. how can people
use this
to share
opinion and expertise
?

30. LLD
needs
feedback mechanisms

31. comments?
voting?
q&a?
edits?

32. i tried
edits
using version control

33. w/MeSH

34. MeSH Browser

35. static
up-to-date
opaque URIs
read-only

36. 3 years of MeSH history as version-control-backed LLD

38. dynamic
up-to-date, plus history
(mappably) cool URIs
read/write

39. cloneable
forkable
editable locally
pushable
mergable
etc.able

40. not all roses

41. uninteresting diffs
awkward file names
lots of files per dir
serialization issues

42. but lots of possibilities

43. anybody could
add
comments

44. anybody could
clone for
local use

45. anybody could
fork
and submit patches

46. but

47. who would
share
opinions and expertise?

49. who would
share
opinions and expertise?

50. same people as do now

51. Vegans!

52. well,
Vegans and catalogers.

53. we do this work now in
private,
proprietary
systems

54. take
back-room systems
and
put them on the web
or, at least, output from them

55. use URIs as names for things
use HTTP URIs
provide useful information
include links to other URIs
http://www.w3.org/DesignIssues/LinkedData.html

56. mix in
versioning,
commenting

57. sh w
t
a ra
th
ar eb is
d fo
g s
e
in
in i
r b
d ?
te
a e
g
l
h
su
s w
Linked LibraryoData
n
o
e
C
p
h
I
t
sn’t in
Wa io
y fo
n
h r
s
W

58. the w
eb is
sharin for
the web is g data
for
sharing opi
nions
Linked Library Data lted?
on su
sn’t IC
W a
W hy

59. thanks!
@dchud