SlideShare a Scribd company logo
1 of 43
Download to read offline
DOROTHEA SALO

UNIVERSITY OF WISCONSIN

SOYLENT SEM-WEB PLE!
EO
P
IS

So hello, guten morgen. My name is Dorothea Salo, and I teach many nerdy things, linked data among them, at the
School of Library and Information Studies at the University of Wisconsin at Madison. I first want to say vielen dank
-- thank you VERY much -- for inviting me here, and I hope I can kick off this conference in a fun and useful way.
Soylent Green DVD cover, c. 2007.
Fair use asserted.
In 1973 Charlton Heston starred in a science-fiction movie called Soylent Green. And it’s a terrible movie, talky
and preachy and weirdly acted and often just dumb. So I don’t feel too bad about spoiling the big plot twist. In the
movie, the environment has degraded so badly that food can’t be grown, so what everybody eats is artificial foods
called Soylent Whatever -- Soylent Red, Soylent Yellow, and the brand-new Soylent Green.
What they don’t know, until Charlton Heston yells it at the end of the movie, is that Soylent Green Is People! More
specifically, Soylent Green is what happens when you make people into food. Ew. But the total nastiness of
cannibalism aside, what’s interesting about this movie is that you have this whole society that has absolutely NO
IDEA that it’s completely dependent on people for its survival!
DOROTHEA SALO

UNIVERSITY OF WISCONSIN

SOYLENT SEM-WEB PLE!
EO
P
IS

It’s the year 2013... Data are still the same.
We’ll do anything to make sense of them.
And for that we need PEOPLE.
Now, we’re not cannibals here in Hamburg, we don’t actually eat people. I hope. No, but seriously, the parallel I
want to draw here is that the original Semantic Web vision curiously lacked PEOPLE, except maybe as the end-user
beneficiaries of linked data. I mean, you can go back and look at what Berners-Lee and his cronies wrote, and you
have all these people booking travel and getting health care or whatever because of all the nice clean shiny RDF
data whizzing around in nice clean shiny server rooms, sure. But the data whizzes around all by itself. Doesn’t
need people. There are no people. Just data.
And I just think this is a counterproductive, even dangerous, way to frame the Semantic Web. And still much too
common. *CLICK* So I assert that the Soylent Semantic Web Is People! Because I want a HUMAN semantic web. A
HUMANE semantic web. Technology without people is just dead metal and silicon. Data without people is just
noise.
SOYLENT SEM-WEBIANS!
AR
IBR
L
IS

It’s the year 2013... Data are still the same.
We’ll do anything to make sense of them.
And for that we need LIBRARIANS.
And more, since we’re here at Semantic Web in Libraries, I will assert that Soylent Semantic Web Is Librarians! We
are the Semantic Web, and the Semantic Web is us!
And I know that isn’t completely news -- we invented SKOS, we invented Dublin Core, we have Karen Coyle and
Diane Hillmann and Ed Summers, just for starters -- but if you had to ask me why this specific conference is
important? That’s what I’d say. The Soylent Semantic Web Is Librarians.
Image credits
• Server room: Alex, “servers”
• http://www.flickr.com/photos/40987321@N02/5580348753/

• Bulldozer: GlacierNPS, “The rotary plow”
• (snow-thrower, not bulldozer, but who’s counting?)
• http://www.flickr.com/photos/glaciernps/7256028570/

• Graph: Jörg Kanngießer, “Graph of klick.JÖrg - Die Homepage”
• http://www.flickr.com/photos/derletzteschrei/193506552/

• Librarians: Charles Greenberg, “IMGP0420”
• http://www.flickr.com/photos/openknowledge/7610237288/

• All these images licensed CC-BY. Thank you, creators!
While we glance at the photo credits, I’ll tell you that what I want to do today is explain my thoughts about why
the Semantic Web is not soylent, not made of librarians, not made of people. I want to explain why it SHOULD be
soylent. And I want to challenge you in specific ways to MAKE it soylent. My ultimate goal, which I imagine you
share, is strengthening library adoption of linked data.
Librarians

BUILD SYSTEMS
CROSSWALK TO
ARCHIVE
MODEL
MAKE
HOST
FOR
linked data
So let’s decide, in approved RDF-triple style, just what properties we can assert about librarians and linked data.
And the usual properties I would expect people at this conference to suggest would be the technical ones.
Librarians MODEL linked data. Librarians CROSSWALK TO linked data. Maybe as simple as librarians MAKE linked
data. Librarians HOST linked data. Librarians ARCHIVE linked data. Librarians BUILD SYSTEMS FOR, and around,
linked data.
But none of those properties really belong to the Soylent Semantic Web, the Semantic Web made of people. These
properties are about the DATA, not the PEOPLE.
Librarians

ADVOCATE FOR
LEARN ABOUT
TEACH ABOUT
INVESTIGATE
ADOPT
DISCUSS
linked data
Here are some things librarians do, as people, in the Soylent Semantic Web. We INVESTIGATE linked data. We
DISCUSS linked data, sometimes not as knowledgeably as linked-data advocates might like. We LEARN ABOUT
linked data. We TEACH ABOUT linked data. We ADVOCATE FOR linked data. Or don’t. And now we get to the
crucial point: we ADOPT linked data.
Librarians

MOSTLY DON’T
ADOPT
linked data

Or we don’t. And we don’t because the Semantic Web community, librarians included, hasn’t acknowledged that it
needs to be soylent. We forget that the Semantic Web is made of people, lots of different kinds of people, some of
them people who are not like us and do not do the same work we do and do not have the same understandings
we have. We forget that we NEED our own librarian colleagues to help us make the Semantic Web, and put library
data into it -- and when we forget our librarian colleagues, our librarian colleagues forget us, and forget linked
data. And that’s not good.
Anfuehrer, “Der Fleischwolf bei der Arbeit” CC-BY-SA
http://www.flickr.com/photos/planetbene/4978709667/

And as I talk to librarians about linked data, what I hear back is that they feel ground up into hamburger -- sorry,
sorry, I had to -- by the whole thing, because the way it’s usually explained to them, it’s so abstract and so
divorced from the actual library work they know. The linked data movement can show them graphs, but it can’t
show them interfaces for doing their work. It can tell them about triples, but it’s not telling them how the catalog
will work if their Internet connection fails. It can explain ontologies, but not how they’ll navigate them.
After one explanatory talk I gave, I had one cataloger tell me with immense frustration, “I just don’t see how this
will WORK!” And I didn’t have a good answer for her. Because I don’t see that either.
THIS HAS HAPPENED

BEFORE
Now, switching away from Soylent Green briefly to -- anybody recognize this? I took it from the remade Battlestar
Galactica television series, which has this catchphrase, “this has happened before.” This is not the first time an
upstart technology has tried to upend an entire established infrastructure, along with the people using it.
XML

IN PUBLISHING

At the turn of the century, I was working in publishing. Specifically, electronic publishing. Even MORE specifically,
ebooks. And while some of the big journal publishers climbed onto the XML bandwagon, many other journals
didn’t, and the trade publishing industry just never did. I remember sitting in an ebook conference next to a highlevel editor from a Big New York Publisher, and we were listening to a fairly basic, fairly standard introduction to
XML, and I heard her sigh “This is just not my world any more.” She felt alienated. She felt ALIEN. Is there anybody
in this room who hasn’t heard a colleague express that alienation?
Even worse, XML didn’t make publishers’ lives easier -- it made them harder! Editing, typesetting, indexing, all
these workflows got hugely more complicated for what looked at the time like super-dubious returns. And the
XML community took no notice whatever of their difficulties, the difficulties ACTUAL PEOPLE were having doing
ACTUAL WORK with XML. Why? Because the XML community was having way too much fun loudly proclaiming
XML’s superiority over everything ever, and going off into corners to have arcane technical arguments about XML
namespaces. Not very soylent! Not humane! Not made of people!
Now, publishers did still make some XML, I grant you. I saw a lot of it. Forgive my language, but trade publisher
XML was CRAP. It was garbage. You wouldn’t feed it to your pet Cylon, it was so bad. Which goes to show that
technology that doesn’t fit into real people’s environments won’t be used properly, if it’s used at all.
INSTITUTIONAL
REPOSITORIES
IN ACADEME

How many of you knew this slide was coming? Go ahead, raise your hands. Yeah. If you know me, you know that I
am just so sad and angry about institutional repositories. In Europe, I know, it hasn’t been quite so bad, but in the
States, it’s been WRETCHED.
But it was the same thing again. There was this technology that was going to make EVERYTHING BETTER, only the
people making the technology forgot all about the people who were supposedly going to use it! So we got these
stupid unusable unfixable systems that did stupid things, and no big surprise, nobody willingly put anything in
them! Because they weren’t soylent! They weren’t made of people!
Incidentally, what happened to the people running institutional repositories? People like me? Well, we got blamed.
And I, for one, got OUT. I will NEVER work on an institutional repository again. This is a thing that happens when
systems don’t treat worker-people well. Worker-people abandon those systems, even people who truly believed in
them and had high hopes for them.
So when we lose catalogers, I think it’s a serious problem.
TH I S WILL HAPPE N

AGAIN
So we have plenty of history of technologies not succeeding because they aren’t people-conscious enough. This
will happen again, to linked data, if we’re not careful. If the Semantic Web doesn’t remember that it’s soylent -made of people. I don’t want that. You don’t want that. But that’s what’s going to happen if we can’t bring more
PEOPLE to linked data.
3:
01
T2
SIS
t Auced)
e areprod
lid not
a sl slide
on (actua
en
Se

“RDF is built from XML.”
It’s the year 2013... RDF is still the same.
Why do people who should know better
still believe RDF is based on XML?
Just as an example, I was at ASIST a couple of weeks ago, the big annual conference for the Association for
Information Science and Technology. And I went to a session on linked data -- and I won’t be any more clear than
that, because I’m not here to embarrass any specific person -- and I saw this on a slide. *CLICK*. RDF is built from
XML.
This kind of thing makes me think that eating people alive might actually be an interesting lifestyle choice! Maybe
you too? *CLICK* Because my gosh, it’s twenty-thirteen, RDF never was built from XML, so why on earth do people
who really should know better still believe this strongly enough to put it on a presentation slide?!
So clearly education, even REALLY BASIC education, is a problem here. And it’s a PEOPLE problem, not a data
problem.
Rex Pe, “student teacher” CC-BY
http://www.flickr.com/photos/goldendragon613/250121512/

And as an educator, it’s MY PROBLEM, right? I think of education as my major role in furthering the adoption of
linked data in libraries. Educating future librarians and archivists and other information professionals. Educating
CURRENT ones, which I also do.
I gotta tell you, though, that current linked data infrastructure is NOT making this easy for me.
1000

1000

(essentially
infinite)
750

500

250
150
90

0

45

HTML5

HTML5 / CSS

XML (MODS)

RDF

Teaching time for minimal competence
(in minutes)
Give me forty-five minutes, and I can drag a roomful of complete HTML novices through making an extremely
basic web page. I know this because I’ve done it! Give me another forty-five minutes, and I can drag those same
people through the basics of CSS. Again, I know this because I’ve DONE it. And yeah, they won’t be web designers
after that, but they can go and practice usefully on their own and get better, and there’s a TON of resources on
the web to help them.
XML is a bit harder to explain and work with. But. If my roomful of people is actually a roomful of librarians or
library-school students? I can drag them through being able to make a basic MODS record in two and a half hours
or so. I know this. I’ve done it.
*CLICK* Here’s the thing. I don’t know how much time it takes to drag a roomful of novices through minimal RDF
competence. I’m not even sure what minimal RDF competence LOOKS like! So essentially it might as well be
infinite time. I’ve tried, I really have. I just don’t think I’ve succeeded. What are the problems I’m running into?
Dave Hosford, “Diving Board Catch” CC-BY
http://www.flickr.com/photos/baltimoredave/4813902094/

Part of my problem is that the training materials I have to work with force my librarian learners into stunts like
trying to catch a ball while jumping off a diving board. Really, a lot of the stuff that’s out there, even I bounce
right off of -- and I supposedly know RDF well enough to keynote a semantic-web conference!
Davide Palmisano, “Introduction to Linked Data.” Fair use asserted.
http://www.cambridgesemantics.com/semantic-university/introduction-to-linked-data

Here’s a linked-data introduction from Cambridge Semantics -- and in fairness to them, they didn’t make this for
librarians, but it’s still one of the best things out there. But look at it. Just the first sentence *CLICK* and we’ve
already brought in H-T-T-P and T-C-P-I-P without defining them, much less explaining why they’re important in
this context. My learners? My librarians and library-school students? They don’t know about the alphabet-soup
plumbing of the Internet! They might have heard H-T-T-P and T-C-P-I-P mentioned (quite likely by me, in
another class), but that doesn’t mean they KNOW. They’re just going to bounce right off this, or get distracted by
something that’s actually a pretty minor and useless detail.
It gets worse. What’s the metaphor this intro picked out, to explain linked data? *CLICK* The relational database!
Speaking of things a lot of my learners don’t know about!
So this extremely well-intentioned and well-written tutorial is useless to me. It won’t help the people I have to
teach, so it’s NOT SOYLENT.
Sarah Deer, “duh” CC-BY
http://www.flickr.com/photos/sarahdeer/3666261790/

The answer to this dilemma is not to call my learners stupid. I warn you, I am not even going to LISTEN to that, so
don’t anybody try it.
I’m also not going to listen to any suggestion that librarians can’t learn about linked data until they learn T-C-PI-P and H-T-T-P and relational databases and XML and at least three programming languages. That’s ridiculous.
I’ve been teaching tech to future librarians since oh-seven, and trust me, with most things you can meet them
where they are -- which can, yes, be a REALLY low skill level -- and still teach them a lot.
B.S. Wise, “humanity. love. respect” CC-BY
http://www.flickr.com/photos/bswise/4621075758/
How does that work? The answer -- the SOYLENT answer, the answer that acknowledges my learners’ HUMANITY
and their LOVE for what they do -- the answer is respect. Primarily, respect for librarians’ existing knowledge
base. And this is the principle I try to build my lessons on -- draw from what my learners already know.
I start with

METADATA
MARC
because they get it.
So I try to teach linked data based on my learners’ interest in it. No surprise, for most of them, their interest has a
lot to do with linked data replacing MARC. *CLICK* The rest of them are digital librarians and archivists, or
aspiring digital librarians at any rate, and for them I keep library metadata practices in mind.
*CLICK* So, for the sake of time, let’s just stick to MARC. What happens when I try to translate MARC skills and
practices into a linked-data context?
xlibber, “Bad Parking” CC-BY
http://www.flickr.com/photos/xlibber/3870106899/
What happens is the same thing that happened with publishers and XML -- I crash my little linked-data car RIGHT
INTO all the work that libraries now do, all the work that forms the FOUNDATIONS of library data, that is just
IMPOSSIBLE to even DEMONSTRATE with linked data.
I won’t tell you all my tales of woe -- I have a lot of them! -- but here’s one. I teach this continuing-education
course that introduces XML and linked data to working librarians. This fall I wanted to add a couple of weeks on
Open Refine to it. Because I thought that data cleanup was important to teach, for starters. And I thought that
reconciling some random spreadsheet metadata with existing linked data stores would be a cool demo, with
pretty obvious relevance to real-world librarian work.
So naturally I thought about name authority control. Right?! Because it’s just so basic to what librarians do.
Because it’s something the rest of the linked-data world is totally learning to do from libraries! Because even in
the States -- where we’re kind of behind Europe in linked-data experimentation -- even in the States we have
these great name authority linked-datastores, VIAF and the Library of Congress, so I thought this would be EASY.
I learned very quickly, of course, that I can’t use VIAF from Open Refine, because there’s no SPARQL endpoint for
it. And I’m on the record here, so I’ll just say -- YOU tell ME why not.
So, okay, that doesn’t work, what about the Library of Congress? Naturally I went right to the source, Ed Summers,
because who wouldn’t?
Oops. Can’t do authority-control reconciliation THAT way either. And this is where I confess the limits of my own
knowledge: I don’t KNOW how to build a web-available triplestore with a SPARQL endpoint off somebody else’s
data! And this lesson I was working on was two weeks from going live -- I didn’t have time to figure it out!
So I asked if anybody else had maybe done authority control with Open Refine and could show me how. I just
needed a simple demo!
I heard nothing.
So let me just say, trying to put together a useful lesson about how to do ACTUAL LIBRARY WORK with linked data?
Was NOT a super-humane experience. I felt annoyed. I felt stupid. I felt frustrated. I felt like hey, if the Semantic
Web is so soylent, HOW ABOUT I JUST EAT UP ALL YOU LINKED DATA NERDS?
And I am a vegetarian!
Authority control is basic, basic stuff, folks. Many librarians consider it a touchstone of library practice, something
CENTRAL to our professional identities. (So to speak.) If I can’t do authority control with linked data, do not even
TALK to me about how linked data is more flexible, linked data is wonderful, linked data is superior -- linked data
is USELESS. It is useless for librarians in practical terms. That’s not a problem with librarians. That’s a problem
with linked data.
The end of the story, just to add insult to injury, is that THIS happened. Though I was able to fix it, after some
searching and fiddling. And that leads me to another thing I want to talk about, which is the state of tools
available for just messing around with linked data.
These are the instructions for installing the RDF extension for Open Refine -- which, by the way, I think this is
great and I want more things like it. These are the LONG instructions, mind you -- there’s a shorter set on the
main page.
*CLICK* There’s a major error in these; you can’t actually get to the workspace directory from the Open Refine
start page, because the start page starts on the Create tab, not the Open tab. I flatter myself I’m pretty tech-savvy,
but I had to click around and swear a bit before I figured out what these instructions were getting at.
So I wrote my own installation instructions, that seemed to work pretty well. You’re welcome. PLEASE don’t make
me do this again. Wrong installation instructions are just NOT SOYLENT. And this installation method? Is ridiculous
on its face. Not soylent at all.
If there are better tools -- tools that help me... help my learners... get ACTUAL LIBRARY WORK DONE with linked
data, I do not know what they are. I’m not sure they even EXIST. And that’s a gigantic problem for me as an
educator, and ultimately it’s a gigantic problem for you and for linked data. If I fail at my job, you know what
happens.
XML

IN PUBLISHING

It’s what happened with XML and publishing, where XML did NOT HELP get publishing work done.
INSTITUTIONAL
REPOSITORIES
IN ACADEME

It’s what happened with institutional repositories, which basically didn’t help ANYBODY get any work done.
Rob Boudon, “Jamie Lyon - YAY WOW” CC-BY
http://www.flickr.com/photos/robboudon/6052727720/

Soylent technologies, technologies that are so respectful of people that people jump for joy about using them,
HELP THOSE PEOPLE GET STUFF DONE. It’s as simple as that. And this needs to be true for people who are NOT
linked data nerds and NOT programmers.
Look, fundamentally, this is the same reason programmers hate MARC! MARC gets in the way of programmers
getting useful work done, right? But if linked data puts every other librarian on earth in the position that library
programmers are currently in? That’s not going to help linked-data adoption in libraries.
NEGATIVE
PATH
DEPENDENCE
Colby Stopa, “Path” CC-BY
http://www.flickr.com/photos/photographybycolby/10169675563/
So to sum up here... because I can’t educate people well, and because the tools are so bad, and because
practically nobody can actually get library work done with linked data, linked data is stuck *CLICK* in what I’ve
seen called NEGATIVE PATH DEPENDENCE. What’s negative path dependence? I quote from a recent report on data
sharing: “Because of high switching costs, inferior technologies can become so dominant that even superior
technologies cannot surpass them in the marketplace.” Sounds like XML in publishing, right, compared to PDF?
Sounds like institutional repositories against journals, right?
I’m afraid it sounds like linked data against MARC, too. Meaning no disrespect at all to the great Henriette Avram,
MARC is the inferior technology here! I really believe that! But linked data, despite its superiority, can’t get library
work done at this point without ridiculous costs, so it can’t replace MARC.
But. It doesn’t have to be this way. This I also believe.
FOUR HCHALLENGES-WEB
T SEM
OYLEN
ES
FOR T

So I’ll close with four challenges for the Soylent Semantic Web, the Semantic Web that is made of librarians and
other people. I hope -- and I believe! -- that presenters at this conference will answer these challenges, and I look
forward to seeing that... and I also hope that all of you take these challenges home and work on them.
Challenge #1:

WORK, NOT
ONTOLOGIES
for linked data
Here is my linked-data heresy. Feel free to turn me into hamburger for it later: I don’t CARE about your ontology. I
don’t care about ANYBODY’s ontology, or data model, or graph, or whatever. I. Do not. CARE. Why should I? We’ve
done library work without ontologies and picture-perfect data models for hundreds of years. Somehow or other.
Can we just get off ontologies already?
What I care about? I care about the WORK I can do with linked data, and the work librarians can do with linked
data, and the work my learners can do with linked data. I care about the tools that help them do that work. I care
about the work skills I can realistically teach my learners that someone will pay them for -- and before you say
anything, “knowing an ontology” is NOT something employers are gonna pay for!
So I don’t need ontologies. I need well-documented linked-data tools that I can use and teach. I need linked-data
workflows, based on real-world problems and real-world solutions, that I can demonstrate and imitate. I need
linked-data systems that do REAL LIBRARY WORK, right out of the box. And very little of this exists today, because
too much of the linked-data community is off in corners having arcane discussions about OWL same-as and H-TT-P range fourteen. Just like XML namespaces back in the day! And I’m saying, STOP THAT. Before you write ONE
MORE LINE of OWL or R-D-F Schema, write code that lets real live people do real-world work with linked data.
Challenge #2:

IT’S ABOUT
IT’SNOT ABOUT
WHAT YOU CAN DO
WHAT I CAN DO
with linked data
When I was running institutional repositories, I went to conferences about them, as ya do. And at those
conferences I saw a LOT of demos of new and innovative software hacks. And a lot of those demos were
absolutely amazing -- but they were completely irrelevant to me, because they were impossible to implement in
my environment. So I challenge everyone here, because you are all experts already, to stop thinking about what
YOU can do with linked data *CLICK* and instead think about what *I* can do with linked data.
And what my learners can do. And what catalogers and metadata librarians and digital-library managers and
institutional-repository managers and reference librarians can do! Because if YOU are the only one who can do
what you do with linked data, librarianship writ large will NEVER be able to do it. And if you think this is a stealth
demand for better tool usability, you’re absolutely right, it is! But that’s not all it is.
This means that you need to learn about what I do, and what I CAN do. And what catalogers and metadata
librarians and all the rest of us do, right? Maybe actually watching us do it? Maybe doing some of it yourselves?
Yeah. So I challenge you to be curious about my work environment, as an educator. And catalogers’ work
environments. And digital-library work environments. Find out about those, firsthand, and use what you learn to
build linked-data systems that all librarians and libraries benefit from.
Challenge #3:

WOW
WOW ME!
LIBRARIANSHIP
with linked data
My third challenge, and I’m quite hopeful about this one, actually -- make me say WOW! about something you did
with linked data. *CLICK* And why stop at me? I challenge you to wow all of librarianship with linked data!
Some of you may remember the rollout of the Endeca-based library catalog at North Carolina State University in
the mid-two-thousands. For those of you who don’t recall, it was this ONE CATALOG that started the whole
discovery-layer movement. And what I remember most about that was that the new catalog got basically zero
pushback from librarianship generally. Even though it was a HUGE change where you’d normally expect a lot of
negative path dependence to kick in.
Instead, everybody said WOW. Wow, I want that! Wow, look, facets for narrowing searches! Wow, check it out, you
can actually start a query by drilling down through subject headings! Wow, de-duplicated records! Wow, relevance
ranking! It was just a giant leap forward from what we had. Forget negative path dependence, people wanted this
functionality NOW.
I challenge you to make something for libraries with linked data that has as much wow as that original Endeca
catalog did. So much wow that nobody even argues about linked data because everybody wants what it can do.
Challenge #4:

DISRUPT MARC
with linked data
Okay, I’m just gonna say this: If we want MARC dead? And we do! We’re gonna have to kill it ourselves and eat the
evidence. But I have a different idea about how to do this than I think most librarians in the linked-data space do. I
see linked-data effort focusing on big national libraries, big academic libraries, big consortia, nothing but bigbig-big.
I’m not sure that’s the right strategy all by itself, to be honest. And I’m sorry for using the word “disrupt” because
I know it’s a giant cliché now, but I’m serious about it. Let me explain what I mean.
w.marsh, “old shelby park library” CC-BY
http://www.flickr.com/photos/40943981@N00/3185725324/
Last summer I taught another continuing-education course for public librarians, about acquiring books from
independent publishers and people who self-publish. And one of my learners, who is a public librarian in a smalltown public library like the one I’m showing here -- she said a very sad thing. There was NO WAY her library
would be able to buy indie or self-published books, not print and not electronic. Just no way. Why not, I asked?
Because there are only two employees at that library, she said, so they can’t do ANY original cataloging!
That librarian and her little tiny two-person library? They’re what disruption theory calls an “underserved market.”
MARC is no good for her -- it’s too complicated and too expensive. If you can make a simple linked-data system
that’s cheaper and easier and more convenient for her, and lets her put in all the books she wants, including indie
books, and lets her patrons find all the books they want, SHE WILL USE IT. And so will a LOT of little tiny libraries
that just can’t do MARC. And if linked data is so easy and so great that little tiny libraries with two employees use
it, what’s everybody else’s excuse, right? If linked data starts small, it can take over the world from MARC! I really
believe this!
Library linked data
FOR GREA JUS
T
TICE

So if you say linked data is so much better than MARC, I’m saying prove it, for great justice!
Okay, okay, last nerd joke, I promise. But the serious point behind the joke is that there really is a social justice
issue here! Linked data shouldn’t be something that only helps big libraries and their librarians. Let’s build small
first, and build up from there, and then we can help ALL libraries, all librarians, and ALL library patrons.
I think a linked-data catalog... that small libraries and their librarians can actually USE, and is demonstrably better
than what they have... can be built. Right now, today, it can be built. I challenge you to build it, for great justice -including justice within librarianship for linked data.
Vielen dank!
Dorothea Salo
salo@wisc.edu
This presentation is available under a
Creative Commons 3.0 Attribution
United States license.
Please respect CC licenses on photos if you reuse.
So once again, thanks for having me, and I look forward to the rest of the conference!

More Related Content

What's hot

Educators & Librarians in SL
Educators & Librarians in SLEducators & Librarians in SL
Educators & Librarians in SLLorri Mon
 
Gavin Bell Toc09 Long Tail Needs Community Sm
Gavin Bell Toc09 Long Tail Needs Community SmGavin Bell Toc09 Long Tail Needs Community Sm
Gavin Bell Toc09 Long Tail Needs Community SmGavin Bell
 
Social Software and Publishers - Gavin Bell - O'Reilly Tools of Change 2007
Social Software and Publishers - Gavin Bell - O'Reilly Tools of Change 2007Social Software and Publishers - Gavin Bell - O'Reilly Tools of Change 2007
Social Software and Publishers - Gavin Bell - O'Reilly Tools of Change 2007Gavin Bell
 
MW2011: Cope, A., Authority Records, Future Computers and Other Unfinished Hi...
MW2011: Cope, A., Authority Records, Future Computers and Other Unfinished Hi...MW2011: Cope, A., Authority Records, Future Computers and Other Unfinished Hi...
MW2011: Cope, A., Authority Records, Future Computers and Other Unfinished Hi...museums and the web
 
Academic Library Journal Panic
Academic Library Journal PanicAcademic Library Journal Panic
Academic Library Journal PanicTeam 144L
 
Closing Plenary: National Digital Forum
Closing Plenary: National Digital ForumClosing Plenary: National Digital Forum
Closing Plenary: National Digital ForumGeorge Oates
 
Researchers, Discovery and the Internet: What Next?
Researchers, Discovery and the Internet: What Next?Researchers, Discovery and the Internet: What Next?
Researchers, Discovery and the Internet: What Next?David Smith
 
To borg or not to borg - individual vs collective, Gavin Bell fowa08
To borg or not to borg - individual vs collective, Gavin Bell fowa08To borg or not to borg - individual vs collective, Gavin Bell fowa08
To borg or not to borg - individual vs collective, Gavin Bell fowa08Gavin Bell
 
I barely have time for my first life, why do I need a Second Life?
I barely have time for my first life, why do I need a Second Life?I barely have time for my first life, why do I need a Second Life?
I barely have time for my first life, why do I need a Second Life?Alice Ruleman
 
Miscellaneous Connections
Miscellaneous ConnectionsMiscellaneous Connections
Miscellaneous ConnectionsMal Booth
 
Social Media for the Scared February 2014
Social Media for the Scared February 2014Social Media for the Scared February 2014
Social Media for the Scared February 2014Bex Lewis
 
Web 2.0: How to Stop Thinking and Start Doing: Addressing Organisational Barr...
Web 2.0: How to Stop Thinking and Start Doing: Addressing Organisational Barr...Web 2.0: How to Stop Thinking and Start Doing: Addressing Organisational Barr...
Web 2.0: How to Stop Thinking and Start Doing: Addressing Organisational Barr...lisbk
 
Where are Repository's Going?
Where are Repository's Going?Where are Repository's Going?
Where are Repository's Going?benosteen
 
Scanned and Delivered: How the DHLab made remote research work
Scanned and Delivered: How the DHLab made remote research workScanned and Delivered: How the DHLab made remote research work
Scanned and Delivered: How the DHLab made remote research workYHRUploads
 

What's hot (20)

Educators & Librarians in SL
Educators & Librarians in SLEducators & Librarians in SL
Educators & Librarians in SL
 
Gavin Bell Toc09 Long Tail Needs Community Sm
Gavin Bell Toc09 Long Tail Needs Community SmGavin Bell Toc09 Long Tail Needs Community Sm
Gavin Bell Toc09 Long Tail Needs Community Sm
 
Social Software and Publishers - Gavin Bell - O'Reilly Tools of Change 2007
Social Software and Publishers - Gavin Bell - O'Reilly Tools of Change 2007Social Software and Publishers - Gavin Bell - O'Reilly Tools of Change 2007
Social Software and Publishers - Gavin Bell - O'Reilly Tools of Change 2007
 
MW2011: Cope, A., Authority Records, Future Computers and Other Unfinished Hi...
MW2011: Cope, A., Authority Records, Future Computers and Other Unfinished Hi...MW2011: Cope, A., Authority Records, Future Computers and Other Unfinished Hi...
MW2011: Cope, A., Authority Records, Future Computers and Other Unfinished Hi...
 
Academic Library Journal Panic
Academic Library Journal PanicAcademic Library Journal Panic
Academic Library Journal Panic
 
Closing Plenary: National Digital Forum
Closing Plenary: National Digital ForumClosing Plenary: National Digital Forum
Closing Plenary: National Digital Forum
 
Researchers, Discovery and the Internet: What Next?
Researchers, Discovery and the Internet: What Next?Researchers, Discovery and the Internet: What Next?
Researchers, Discovery and the Internet: What Next?
 
To borg or not to borg - individual vs collective, Gavin Bell fowa08
To borg or not to borg - individual vs collective, Gavin Bell fowa08To borg or not to borg - individual vs collective, Gavin Bell fowa08
To borg or not to borg - individual vs collective, Gavin Bell fowa08
 
I barely have time for my first life, why do I need a Second Life?
I barely have time for my first life, why do I need a Second Life?I barely have time for my first life, why do I need a Second Life?
I barely have time for my first life, why do I need a Second Life?
 
Miscellaneous Connections
Miscellaneous ConnectionsMiscellaneous Connections
Miscellaneous Connections
 
Fontana
FontanaFontana
Fontana
 
Social Media for the Scared February 2014
Social Media for the Scared February 2014Social Media for the Scared February 2014
Social Media for the Scared February 2014
 
Interactive Trends
Interactive TrendsInteractive Trends
Interactive Trends
 
Web 2.0: How to Stop Thinking and Start Doing: Addressing Organisational Barr...
Web 2.0: How to Stop Thinking and Start Doing: Addressing Organisational Barr...Web 2.0: How to Stop Thinking and Start Doing: Addressing Organisational Barr...
Web 2.0: How to Stop Thinking and Start Doing: Addressing Organisational Barr...
 
Where are Repository's Going?
Where are Repository's Going?Where are Repository's Going?
Where are Repository's Going?
 
Thumbs up!
Thumbs up!Thumbs up!
Thumbs up!
 
Scanned and Delivered: How the DHLab made remote research work
Scanned and Delivered: How the DHLab made remote research workScanned and Delivered: How the DHLab made remote research work
Scanned and Delivered: How the DHLab made remote research work
 
Hacking Libraries
Hacking LibrariesHacking Libraries
Hacking Libraries
 
One Big Library
One Big LibraryOne Big Library
One Big Library
 
Curation North Carolina
Curation North CarolinaCuration North Carolina
Curation North Carolina
 

Viewers also liked

Preservation and institutional repositories for the digital arts and humanities
Preservation and institutional repositories for the digital arts and humanitiesPreservation and institutional repositories for the digital arts and humanities
Preservation and institutional repositories for the digital arts and humanitiesDorothea Salo
 
So are we winning yet?
So are we winning yet?So are we winning yet?
So are we winning yet?Dorothea Salo
 
Open Sesame (and other open movements)
Open Sesame (and other open movements)Open Sesame (and other open movements)
Open Sesame (and other open movements)Dorothea Salo
 
Manufacturing Serendipity
Manufacturing SerendipityManufacturing Serendipity
Manufacturing SerendipityDorothea Salo
 
RDF, RDA, and other TLAs
RDF, RDA, and other TLAsRDF, RDA, and other TLAs
RDF, RDA, and other TLAsDorothea Salo
 
I own copyright, so I pwn you!
I own copyright, so I pwn you!I own copyright, so I pwn you!
I own copyright, so I pwn you!Dorothea Salo
 
So are we winning yet?
So are we winning yet?So are we winning yet?
So are we winning yet?Dorothea Salo
 
Even the Loons are Licensed
Even the Loons are LicensedEven the Loons are Licensed
Even the Loons are LicensedDorothea Salo
 
Solving Problems with Web 2.0
Solving Problems with Web 2.0Solving Problems with Web 2.0
Solving Problems with Web 2.0Dorothea Salo
 
A Successful Failure: Community Requirements Gathering for DSpace
A Successful Failure: Community Requirements Gathering for DSpaceA Successful Failure: Community Requirements Gathering for DSpace
A Successful Failure: Community Requirements Gathering for DSpaceDorothea Salo
 
Lipstick on a Pig: Integrated Library Systems
Lipstick on a Pig: Integrated Library SystemsLipstick on a Pig: Integrated Library Systems
Lipstick on a Pig: Integrated Library SystemsDorothea Salo
 
Save the Cows! Cyberinfrastructure for the Rest of Us
Save the Cows! Cyberinfrastructure for the Rest of UsSave the Cows! Cyberinfrastructure for the Rest of Us
Save the Cows! Cyberinfrastructure for the Rest of UsDorothea Salo
 
What's Driving Open Access?
What's Driving Open Access?What's Driving Open Access?
What's Driving Open Access?Dorothea Salo
 
Grab a bucket! It's raining data!
Grab a bucket! It's raining data!Grab a bucket! It's raining data!
Grab a bucket! It's raining data!Dorothea Salo
 
So you think you know libraries
So you think you know librariesSo you think you know libraries
So you think you know librariesDorothea Salo
 

Viewers also liked (20)

Preservation and institutional repositories for the digital arts and humanities
Preservation and institutional repositories for the digital arts and humanitiesPreservation and institutional repositories for the digital arts and humanities
Preservation and institutional repositories for the digital arts and humanities
 
Metadata
MetadataMetadata
Metadata
 
So are we winning yet?
So are we winning yet?So are we winning yet?
So are we winning yet?
 
Open Sesame (and other open movements)
Open Sesame (and other open movements)Open Sesame (and other open movements)
Open Sesame (and other open movements)
 
Manufacturing Serendipity
Manufacturing SerendipityManufacturing Serendipity
Manufacturing Serendipity
 
Occupy Copyright!
Occupy Copyright!Occupy Copyright!
Occupy Copyright!
 
RDF, RDA, and other TLAs
RDF, RDA, and other TLAsRDF, RDA, and other TLAs
RDF, RDA, and other TLAs
 
I own copyright, so I pwn you!
I own copyright, so I pwn you!I own copyright, so I pwn you!
I own copyright, so I pwn you!
 
Encryption
EncryptionEncryption
Encryption
 
So are we winning yet?
So are we winning yet?So are we winning yet?
So are we winning yet?
 
Even the Loons are Licensed
Even the Loons are LicensedEven the Loons are Licensed
Even the Loons are Licensed
 
Solving Problems with Web 2.0
Solving Problems with Web 2.0Solving Problems with Web 2.0
Solving Problems with Web 2.0
 
Escaping Datageddon
Escaping DatageddonEscaping Datageddon
Escaping Datageddon
 
Who owns our work?
Who owns our work?Who owns our work?
Who owns our work?
 
A Successful Failure: Community Requirements Gathering for DSpace
A Successful Failure: Community Requirements Gathering for DSpaceA Successful Failure: Community Requirements Gathering for DSpace
A Successful Failure: Community Requirements Gathering for DSpace
 
Lipstick on a Pig: Integrated Library Systems
Lipstick on a Pig: Integrated Library SystemsLipstick on a Pig: Integrated Library Systems
Lipstick on a Pig: Integrated Library Systems
 
Save the Cows! Cyberinfrastructure for the Rest of Us
Save the Cows! Cyberinfrastructure for the Rest of UsSave the Cows! Cyberinfrastructure for the Rest of Us
Save the Cows! Cyberinfrastructure for the Rest of Us
 
What's Driving Open Access?
What's Driving Open Access?What's Driving Open Access?
What's Driving Open Access?
 
Grab a bucket! It's raining data!
Grab a bucket! It's raining data!Grab a bucket! It's raining data!
Grab a bucket! It's raining data!
 
So you think you know libraries
So you think you know librariesSo you think you know libraries
So you think you know libraries
 

Similar to Soylent Semantic Web Is People! (with notes)

2013 LIANZA Keynote: River's End
2013 LIANZA Keynote: River's End2013 LIANZA Keynote: River's End
2013 LIANZA Keynote: River's Endgnat
 
Audio in a social Web of linked data
Audio in a social Web of linked dataAudio in a social Web of linked data
Audio in a social Web of linked dataEduserv Foundation
 
social networks and experience design
social networks and experience designsocial networks and experience design
social networks and experience designJames Boardwell
 
Schemas for the Real World [Madison RubyConf 2013]
Schemas for the Real World [Madison RubyConf 2013]Schemas for the Real World [Madison RubyConf 2013]
Schemas for the Real World [Madison RubyConf 2013]Carina C. Zona
 
Is this BIG DATA which I see before me?
Is this BIG DATA which I see before me?Is this BIG DATA which I see before me?
Is this BIG DATA which I see before me?Dorothea Salo
 
Taming Context in the Internet of Things
Taming Context in the Internet of ThingsTaming Context in the Internet of Things
Taming Context in the Internet of ThingsWebVisions
 
Ain't Nobody's Business If I Do (Read Serials)
Ain't Nobody's Business If I Do (Read Serials)Ain't Nobody's Business If I Do (Read Serials)
Ain't Nobody's Business If I Do (Read Serials)NASIG
 
What if you could see through the walls of every museum and something could t...
What if you could see through the walls of every museum and something could t...What if you could see through the walls of every museum and something could t...
What if you could see through the walls of every museum and something could t...Chris Thorpe
 
Designing a Future We Want to Live In - UX STRAT USA 2017
Designing a Future We Want to Live In - UX STRAT USA 2017Designing a Future We Want to Live In - UX STRAT USA 2017
Designing a Future We Want to Live In - UX STRAT USA 2017Andrew Hinton
 
Transforming Our Vision to Enhance Library Services
Transforming Our Vision to Enhance Library ServicesTransforming Our Vision to Enhance Library Services
Transforming Our Vision to Enhance Library ServicesSt. Petersburg College
 
Questions and Answers in a Virtual World : Educators and Librarians as Inform...
Questions and Answers in a Virtual World : Educators and Librarians as Inform...Questions and Answers in a Virtual World : Educators and Librarians as Inform...
Questions and Answers in a Virtual World : Educators and Librarians as Inform...siguse_history
 
Community networks in comics
Community networks in comicsCommunity networks in comics
Community networks in comicsCathy C
 
Sadistic Manipulation and Psychic Liberation in eBook Design
Sadistic Manipulation and Psychic Liberation in eBook DesignSadistic Manipulation and Psychic Liberation in eBook Design
Sadistic Manipulation and Psychic Liberation in eBook DesignEric Swenson
 
Lessons from Webstock ‘12
Lessons from Webstock ‘12Lessons from Webstock ‘12
Lessons from Webstock ‘12JoannaTMcLeod
 
European Cultural Commons Workshop, Introductory Remarks (transcript)
European Cultural Commons Workshop, Introductory Remarks (transcript)European Cultural Commons Workshop, Introductory Remarks (transcript)
European Cultural Commons Workshop, Introductory Remarks (transcript)Michael Edson
 
Open, social and linked - what do current Web trends tell us about the future...
Open, social and linked - what do current Web trends tell us about the future...Open, social and linked - what do current Web trends tell us about the future...
Open, social and linked - what do current Web trends tell us about the future...Andy Powell
 

Similar to Soylent Semantic Web Is People! (with notes) (20)

2013 LIANZA Keynote: River's End
2013 LIANZA Keynote: River's End2013 LIANZA Keynote: River's End
2013 LIANZA Keynote: River's End
 
Audio in a social Web of linked data
Audio in a social Web of linked dataAudio in a social Web of linked data
Audio in a social Web of linked data
 
social networks and experience design
social networks and experience designsocial networks and experience design
social networks and experience design
 
Schemas for the Real World [Madison RubyConf 2013]
Schemas for the Real World [Madison RubyConf 2013]Schemas for the Real World [Madison RubyConf 2013]
Schemas for the Real World [Madison RubyConf 2013]
 
Is this BIG DATA which I see before me?
Is this BIG DATA which I see before me?Is this BIG DATA which I see before me?
Is this BIG DATA which I see before me?
 
Taming Context in the Internet of Things
Taming Context in the Internet of ThingsTaming Context in the Internet of Things
Taming Context in the Internet of Things
 
Ain't Nobody's Business If I Do (Read Serials)
Ain't Nobody's Business If I Do (Read Serials)Ain't Nobody's Business If I Do (Read Serials)
Ain't Nobody's Business If I Do (Read Serials)
 
What if you could see through the walls of every museum and something could t...
What if you could see through the walls of every museum and something could t...What if you could see through the walls of every museum and something could t...
What if you could see through the walls of every museum and something could t...
 
Designing a Future We Want to Live In - UX STRAT USA 2017
Designing a Future We Want to Live In - UX STRAT USA 2017Designing a Future We Want to Live In - UX STRAT USA 2017
Designing a Future We Want to Live In - UX STRAT USA 2017
 
Intranet pecha kucha sydney
Intranet pecha kucha sydneyIntranet pecha kucha sydney
Intranet pecha kucha sydney
 
Web Technologies Final
Web Technologies FinalWeb Technologies Final
Web Technologies Final
 
Transforming Our Vision to Enhance Library Services
Transforming Our Vision to Enhance Library ServicesTransforming Our Vision to Enhance Library Services
Transforming Our Vision to Enhance Library Services
 
Questions and Answers in a Virtual World : Educators and Librarians as Inform...
Questions and Answers in a Virtual World : Educators and Librarians as Inform...Questions and Answers in a Virtual World : Educators and Librarians as Inform...
Questions and Answers in a Virtual World : Educators and Librarians as Inform...
 
Essay On The World Wide Web
Essay On The World Wide WebEssay On The World Wide Web
Essay On The World Wide Web
 
Community networks in comics
Community networks in comicsCommunity networks in comics
Community networks in comics
 
CHLA Slides Rothman
CHLA Slides RothmanCHLA Slides Rothman
CHLA Slides Rothman
 
Sadistic Manipulation and Psychic Liberation in eBook Design
Sadistic Manipulation and Psychic Liberation in eBook DesignSadistic Manipulation and Psychic Liberation in eBook Design
Sadistic Manipulation and Psychic Liberation in eBook Design
 
Lessons from Webstock ‘12
Lessons from Webstock ‘12Lessons from Webstock ‘12
Lessons from Webstock ‘12
 
European Cultural Commons Workshop, Introductory Remarks (transcript)
European Cultural Commons Workshop, Introductory Remarks (transcript)European Cultural Commons Workshop, Introductory Remarks (transcript)
European Cultural Commons Workshop, Introductory Remarks (transcript)
 
Open, social and linked - what do current Web trends tell us about the future...
Open, social and linked - what do current Web trends tell us about the future...Open, social and linked - what do current Web trends tell us about the future...
Open, social and linked - what do current Web trends tell us about the future...
 

More from Dorothea Salo

Risk management and auditing
Risk management and auditingRisk management and auditing
Risk management and auditingDorothea Salo
 
The Canonically Bad (Digital) Humanities Proposal (and how to avoid it)
The Canonically Bad (Digital) Humanities Proposal (and how to avoid it)The Canonically Bad (Digital) Humanities Proposal (and how to avoid it)
The Canonically Bad (Digital) Humanities Proposal (and how to avoid it)Dorothea Salo
 
MARC and BIBFRAME; Linking libraries and archives
MARC and BIBFRAME; Linking libraries and archivesMARC and BIBFRAME; Linking libraries and archives
MARC and BIBFRAME; Linking libraries and archivesDorothea Salo
 
Research Data and Scholarly Communication
Research Data and Scholarly CommunicationResearch Data and Scholarly Communication
Research Data and Scholarly CommunicationDorothea Salo
 
Research Data and Scholarly Communication (with notes)
Research Data and Scholarly Communication (with notes)Research Data and Scholarly Communication (with notes)
Research Data and Scholarly Communication (with notes)Dorothea Salo
 
Librarians love data!
Librarians love data!Librarians love data!
Librarians love data!Dorothea Salo
 
Taming the Monster: Digital Preservation Planning and Implementation Tools
Taming the Monster: Digital Preservation Planning and Implementation ToolsTaming the Monster: Digital Preservation Planning and Implementation Tools
Taming the Monster: Digital Preservation Planning and Implementation ToolsDorothea Salo
 
Manufacturing Serendipity
Manufacturing SerendipityManufacturing Serendipity
Manufacturing SerendipityDorothea Salo
 
Databases, Markup, and Regular Expressions
Databases, Markup, and Regular ExpressionsDatabases, Markup, and Regular Expressions
Databases, Markup, and Regular ExpressionsDorothea Salo
 

More from Dorothea Salo (13)

Risk management and auditing
Risk management and auditingRisk management and auditing
Risk management and auditing
 
The Canonically Bad (Digital) Humanities Proposal (and how to avoid it)
The Canonically Bad (Digital) Humanities Proposal (and how to avoid it)The Canonically Bad (Digital) Humanities Proposal (and how to avoid it)
The Canonically Bad (Digital) Humanities Proposal (and how to avoid it)
 
MARC and BIBFRAME; Linking libraries and archives
MARC and BIBFRAME; Linking libraries and archivesMARC and BIBFRAME; Linking libraries and archives
MARC and BIBFRAME; Linking libraries and archives
 
Library Linked Data
Library Linked DataLibrary Linked Data
Library Linked Data
 
FRBR and RDA
FRBR and RDAFRBR and RDA
FRBR and RDA
 
Research Data and Scholarly Communication
Research Data and Scholarly CommunicationResearch Data and Scholarly Communication
Research Data and Scholarly Communication
 
Research Data and Scholarly Communication (with notes)
Research Data and Scholarly Communication (with notes)Research Data and Scholarly Communication (with notes)
Research Data and Scholarly Communication (with notes)
 
What We Organize
What We OrganizeWhat We Organize
What We Organize
 
Librarians love data!
Librarians love data!Librarians love data!
Librarians love data!
 
Taming the Monster: Digital Preservation Planning and Implementation Tools
Taming the Monster: Digital Preservation Planning and Implementation ToolsTaming the Monster: Digital Preservation Planning and Implementation Tools
Taming the Monster: Digital Preservation Planning and Implementation Tools
 
Manufacturing Serendipity
Manufacturing SerendipityManufacturing Serendipity
Manufacturing Serendipity
 
Open Content
Open ContentOpen Content
Open Content
 
Databases, Markup, and Regular Expressions
Databases, Markup, and Regular ExpressionsDatabases, Markup, and Regular Expressions
Databases, Markup, and Regular Expressions
 

Recently uploaded

activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfJamie (Taka) Wang
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdfPedro Manuel
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationIES VE
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...Aggregage
 
The Kubernetes Gateway API and its role in Cloud Native API Management
The Kubernetes Gateway API and its role in Cloud Native API ManagementThe Kubernetes Gateway API and its role in Cloud Native API Management
The Kubernetes Gateway API and its role in Cloud Native API ManagementNuwan Dias
 
Comparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioComparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioChristian Posta
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-pyJamie (Taka) Wang
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintMahmoud Rabie
 
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1DianaGray10
 
Valere | Digital Solutions & AI Transformation Portfolio | 2024
Valere | Digital Solutions & AI Transformation Portfolio | 2024Valere | Digital Solutions & AI Transformation Portfolio | 2024
Valere | Digital Solutions & AI Transformation Portfolio | 2024Alexander Turgeon
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024SkyPlanner
 
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IES VE
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Websitedgelyza
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDELiveplex
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemAsko Soukka
 
UiPath Studio Web workshop series - Day 5
UiPath Studio Web workshop series - Day 5UiPath Studio Web workshop series - Day 5
UiPath Studio Web workshop series - Day 5DianaGray10
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8DianaGray10
 
99.99% of Your Traces Are (Probably) Trash (SRECon NA 2024).pdf
99.99% of Your Traces  Are (Probably) Trash (SRECon NA 2024).pdf99.99% of Your Traces  Are (Probably) Trash (SRECon NA 2024).pdf
99.99% of Your Traces Are (Probably) Trash (SRECon NA 2024).pdfPaige Cruz
 

Recently uploaded (20)

activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdf
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
 
The Kubernetes Gateway API and its role in Cloud Native API Management
The Kubernetes Gateway API and its role in Cloud Native API ManagementThe Kubernetes Gateway API and its role in Cloud Native API Management
The Kubernetes Gateway API and its role in Cloud Native API Management
 
Comparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioComparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and Istio
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-py
 
201610817 - edge part1
201610817 - edge part1201610817 - edge part1
201610817 - edge part1
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership Blueprint
 
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
 
Valere | Digital Solutions & AI Transformation Portfolio | 2024
Valere | Digital Solutions & AI Transformation Portfolio | 2024Valere | Digital Solutions & AI Transformation Portfolio | 2024
Valere | Digital Solutions & AI Transformation Portfolio | 2024
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024
 
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Website
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystem
 
UiPath Studio Web workshop series - Day 5
UiPath Studio Web workshop series - Day 5UiPath Studio Web workshop series - Day 5
UiPath Studio Web workshop series - Day 5
 
20230104 - machine vision
20230104 - machine vision20230104 - machine vision
20230104 - machine vision
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8
 
99.99% of Your Traces Are (Probably) Trash (SRECon NA 2024).pdf
99.99% of Your Traces  Are (Probably) Trash (SRECon NA 2024).pdf99.99% of Your Traces  Are (Probably) Trash (SRECon NA 2024).pdf
99.99% of Your Traces Are (Probably) Trash (SRECon NA 2024).pdf
 

Soylent Semantic Web Is People! (with notes)

  • 1. DOROTHEA SALO UNIVERSITY OF WISCONSIN SOYLENT SEM-WEB PLE! EO P IS So hello, guten morgen. My name is Dorothea Salo, and I teach many nerdy things, linked data among them, at the School of Library and Information Studies at the University of Wisconsin at Madison. I first want to say vielen dank -- thank you VERY much -- for inviting me here, and I hope I can kick off this conference in a fun and useful way.
  • 2. Soylent Green DVD cover, c. 2007. Fair use asserted. In 1973 Charlton Heston starred in a science-fiction movie called Soylent Green. And it’s a terrible movie, talky and preachy and weirdly acted and often just dumb. So I don’t feel too bad about spoiling the big plot twist. In the movie, the environment has degraded so badly that food can’t be grown, so what everybody eats is artificial foods called Soylent Whatever -- Soylent Red, Soylent Yellow, and the brand-new Soylent Green. What they don’t know, until Charlton Heston yells it at the end of the movie, is that Soylent Green Is People! More specifically, Soylent Green is what happens when you make people into food. Ew. But the total nastiness of cannibalism aside, what’s interesting about this movie is that you have this whole society that has absolutely NO IDEA that it’s completely dependent on people for its survival!
  • 3. DOROTHEA SALO UNIVERSITY OF WISCONSIN SOYLENT SEM-WEB PLE! EO P IS It’s the year 2013... Data are still the same. We’ll do anything to make sense of them. And for that we need PEOPLE. Now, we’re not cannibals here in Hamburg, we don’t actually eat people. I hope. No, but seriously, the parallel I want to draw here is that the original Semantic Web vision curiously lacked PEOPLE, except maybe as the end-user beneficiaries of linked data. I mean, you can go back and look at what Berners-Lee and his cronies wrote, and you have all these people booking travel and getting health care or whatever because of all the nice clean shiny RDF data whizzing around in nice clean shiny server rooms, sure. But the data whizzes around all by itself. Doesn’t need people. There are no people. Just data. And I just think this is a counterproductive, even dangerous, way to frame the Semantic Web. And still much too common. *CLICK* So I assert that the Soylent Semantic Web Is People! Because I want a HUMAN semantic web. A HUMANE semantic web. Technology without people is just dead metal and silicon. Data without people is just noise.
  • 4. SOYLENT SEM-WEBIANS! AR IBR L IS It’s the year 2013... Data are still the same. We’ll do anything to make sense of them. And for that we need LIBRARIANS. And more, since we’re here at Semantic Web in Libraries, I will assert that Soylent Semantic Web Is Librarians! We are the Semantic Web, and the Semantic Web is us! And I know that isn’t completely news -- we invented SKOS, we invented Dublin Core, we have Karen Coyle and Diane Hillmann and Ed Summers, just for starters -- but if you had to ask me why this specific conference is important? That’s what I’d say. The Soylent Semantic Web Is Librarians.
  • 5. Image credits • Server room: Alex, “servers” • http://www.flickr.com/photos/40987321@N02/5580348753/ • Bulldozer: GlacierNPS, “The rotary plow” • (snow-thrower, not bulldozer, but who’s counting?) • http://www.flickr.com/photos/glaciernps/7256028570/ • Graph: Jörg Kanngießer, “Graph of klick.JÖrg - Die Homepage” • http://www.flickr.com/photos/derletzteschrei/193506552/ • Librarians: Charles Greenberg, “IMGP0420” • http://www.flickr.com/photos/openknowledge/7610237288/ • All these images licensed CC-BY. Thank you, creators! While we glance at the photo credits, I’ll tell you that what I want to do today is explain my thoughts about why the Semantic Web is not soylent, not made of librarians, not made of people. I want to explain why it SHOULD be soylent. And I want to challenge you in specific ways to MAKE it soylent. My ultimate goal, which I imagine you share, is strengthening library adoption of linked data.
  • 6. Librarians BUILD SYSTEMS CROSSWALK TO ARCHIVE MODEL MAKE HOST FOR linked data So let’s decide, in approved RDF-triple style, just what properties we can assert about librarians and linked data. And the usual properties I would expect people at this conference to suggest would be the technical ones. Librarians MODEL linked data. Librarians CROSSWALK TO linked data. Maybe as simple as librarians MAKE linked data. Librarians HOST linked data. Librarians ARCHIVE linked data. Librarians BUILD SYSTEMS FOR, and around, linked data. But none of those properties really belong to the Soylent Semantic Web, the Semantic Web made of people. These properties are about the DATA, not the PEOPLE.
  • 7. Librarians ADVOCATE FOR LEARN ABOUT TEACH ABOUT INVESTIGATE ADOPT DISCUSS linked data Here are some things librarians do, as people, in the Soylent Semantic Web. We INVESTIGATE linked data. We DISCUSS linked data, sometimes not as knowledgeably as linked-data advocates might like. We LEARN ABOUT linked data. We TEACH ABOUT linked data. We ADVOCATE FOR linked data. Or don’t. And now we get to the crucial point: we ADOPT linked data.
  • 8. Librarians MOSTLY DON’T ADOPT linked data Or we don’t. And we don’t because the Semantic Web community, librarians included, hasn’t acknowledged that it needs to be soylent. We forget that the Semantic Web is made of people, lots of different kinds of people, some of them people who are not like us and do not do the same work we do and do not have the same understandings we have. We forget that we NEED our own librarian colleagues to help us make the Semantic Web, and put library data into it -- and when we forget our librarian colleagues, our librarian colleagues forget us, and forget linked data. And that’s not good.
  • 9. Anfuehrer, “Der Fleischwolf bei der Arbeit” CC-BY-SA http://www.flickr.com/photos/planetbene/4978709667/ And as I talk to librarians about linked data, what I hear back is that they feel ground up into hamburger -- sorry, sorry, I had to -- by the whole thing, because the way it’s usually explained to them, it’s so abstract and so divorced from the actual library work they know. The linked data movement can show them graphs, but it can’t show them interfaces for doing their work. It can tell them about triples, but it’s not telling them how the catalog will work if their Internet connection fails. It can explain ontologies, but not how they’ll navigate them. After one explanatory talk I gave, I had one cataloger tell me with immense frustration, “I just don’t see how this will WORK!” And I didn’t have a good answer for her. Because I don’t see that either.
  • 10. THIS HAS HAPPENED BEFORE Now, switching away from Soylent Green briefly to -- anybody recognize this? I took it from the remade Battlestar Galactica television series, which has this catchphrase, “this has happened before.” This is not the first time an upstart technology has tried to upend an entire established infrastructure, along with the people using it.
  • 11. XML IN PUBLISHING At the turn of the century, I was working in publishing. Specifically, electronic publishing. Even MORE specifically, ebooks. And while some of the big journal publishers climbed onto the XML bandwagon, many other journals didn’t, and the trade publishing industry just never did. I remember sitting in an ebook conference next to a highlevel editor from a Big New York Publisher, and we were listening to a fairly basic, fairly standard introduction to XML, and I heard her sigh “This is just not my world any more.” She felt alienated. She felt ALIEN. Is there anybody in this room who hasn’t heard a colleague express that alienation? Even worse, XML didn’t make publishers’ lives easier -- it made them harder! Editing, typesetting, indexing, all these workflows got hugely more complicated for what looked at the time like super-dubious returns. And the XML community took no notice whatever of their difficulties, the difficulties ACTUAL PEOPLE were having doing ACTUAL WORK with XML. Why? Because the XML community was having way too much fun loudly proclaiming XML’s superiority over everything ever, and going off into corners to have arcane technical arguments about XML namespaces. Not very soylent! Not humane! Not made of people! Now, publishers did still make some XML, I grant you. I saw a lot of it. Forgive my language, but trade publisher XML was CRAP. It was garbage. You wouldn’t feed it to your pet Cylon, it was so bad. Which goes to show that technology that doesn’t fit into real people’s environments won’t be used properly, if it’s used at all.
  • 12. INSTITUTIONAL REPOSITORIES IN ACADEME How many of you knew this slide was coming? Go ahead, raise your hands. Yeah. If you know me, you know that I am just so sad and angry about institutional repositories. In Europe, I know, it hasn’t been quite so bad, but in the States, it’s been WRETCHED. But it was the same thing again. There was this technology that was going to make EVERYTHING BETTER, only the people making the technology forgot all about the people who were supposedly going to use it! So we got these stupid unusable unfixable systems that did stupid things, and no big surprise, nobody willingly put anything in them! Because they weren’t soylent! They weren’t made of people! Incidentally, what happened to the people running institutional repositories? People like me? Well, we got blamed. And I, for one, got OUT. I will NEVER work on an institutional repository again. This is a thing that happens when systems don’t treat worker-people well. Worker-people abandon those systems, even people who truly believed in them and had high hopes for them. So when we lose catalogers, I think it’s a serious problem.
  • 13. TH I S WILL HAPPE N AGAIN So we have plenty of history of technologies not succeeding because they aren’t people-conscious enough. This will happen again, to linked data, if we’re not careful. If the Semantic Web doesn’t remember that it’s soylent -made of people. I don’t want that. You don’t want that. But that’s what’s going to happen if we can’t bring more PEOPLE to linked data.
  • 14. 3: 01 T2 SIS t Auced) e areprod lid not a sl slide on (actua en Se “RDF is built from XML.” It’s the year 2013... RDF is still the same. Why do people who should know better still believe RDF is based on XML? Just as an example, I was at ASIST a couple of weeks ago, the big annual conference for the Association for Information Science and Technology. And I went to a session on linked data -- and I won’t be any more clear than that, because I’m not here to embarrass any specific person -- and I saw this on a slide. *CLICK*. RDF is built from XML. This kind of thing makes me think that eating people alive might actually be an interesting lifestyle choice! Maybe you too? *CLICK* Because my gosh, it’s twenty-thirteen, RDF never was built from XML, so why on earth do people who really should know better still believe this strongly enough to put it on a presentation slide?! So clearly education, even REALLY BASIC education, is a problem here. And it’s a PEOPLE problem, not a data problem.
  • 15. Rex Pe, “student teacher” CC-BY http://www.flickr.com/photos/goldendragon613/250121512/ And as an educator, it’s MY PROBLEM, right? I think of education as my major role in furthering the adoption of linked data in libraries. Educating future librarians and archivists and other information professionals. Educating CURRENT ones, which I also do. I gotta tell you, though, that current linked data infrastructure is NOT making this easy for me.
  • 16. 1000 1000 (essentially infinite) 750 500 250 150 90 0 45 HTML5 HTML5 / CSS XML (MODS) RDF Teaching time for minimal competence (in minutes) Give me forty-five minutes, and I can drag a roomful of complete HTML novices through making an extremely basic web page. I know this because I’ve done it! Give me another forty-five minutes, and I can drag those same people through the basics of CSS. Again, I know this because I’ve DONE it. And yeah, they won’t be web designers after that, but they can go and practice usefully on their own and get better, and there’s a TON of resources on the web to help them. XML is a bit harder to explain and work with. But. If my roomful of people is actually a roomful of librarians or library-school students? I can drag them through being able to make a basic MODS record in two and a half hours or so. I know this. I’ve done it. *CLICK* Here’s the thing. I don’t know how much time it takes to drag a roomful of novices through minimal RDF competence. I’m not even sure what minimal RDF competence LOOKS like! So essentially it might as well be infinite time. I’ve tried, I really have. I just don’t think I’ve succeeded. What are the problems I’m running into?
  • 17. Dave Hosford, “Diving Board Catch” CC-BY http://www.flickr.com/photos/baltimoredave/4813902094/ Part of my problem is that the training materials I have to work with force my librarian learners into stunts like trying to catch a ball while jumping off a diving board. Really, a lot of the stuff that’s out there, even I bounce right off of -- and I supposedly know RDF well enough to keynote a semantic-web conference!
  • 18. Davide Palmisano, “Introduction to Linked Data.” Fair use asserted. http://www.cambridgesemantics.com/semantic-university/introduction-to-linked-data Here’s a linked-data introduction from Cambridge Semantics -- and in fairness to them, they didn’t make this for librarians, but it’s still one of the best things out there. But look at it. Just the first sentence *CLICK* and we’ve already brought in H-T-T-P and T-C-P-I-P without defining them, much less explaining why they’re important in this context. My learners? My librarians and library-school students? They don’t know about the alphabet-soup plumbing of the Internet! They might have heard H-T-T-P and T-C-P-I-P mentioned (quite likely by me, in another class), but that doesn’t mean they KNOW. They’re just going to bounce right off this, or get distracted by something that’s actually a pretty minor and useless detail. It gets worse. What’s the metaphor this intro picked out, to explain linked data? *CLICK* The relational database! Speaking of things a lot of my learners don’t know about! So this extremely well-intentioned and well-written tutorial is useless to me. It won’t help the people I have to teach, so it’s NOT SOYLENT.
  • 19. Sarah Deer, “duh” CC-BY http://www.flickr.com/photos/sarahdeer/3666261790/ The answer to this dilemma is not to call my learners stupid. I warn you, I am not even going to LISTEN to that, so don’t anybody try it. I’m also not going to listen to any suggestion that librarians can’t learn about linked data until they learn T-C-PI-P and H-T-T-P and relational databases and XML and at least three programming languages. That’s ridiculous. I’ve been teaching tech to future librarians since oh-seven, and trust me, with most things you can meet them where they are -- which can, yes, be a REALLY low skill level -- and still teach them a lot.
  • 20. B.S. Wise, “humanity. love. respect” CC-BY http://www.flickr.com/photos/bswise/4621075758/ How does that work? The answer -- the SOYLENT answer, the answer that acknowledges my learners’ HUMANITY and their LOVE for what they do -- the answer is respect. Primarily, respect for librarians’ existing knowledge base. And this is the principle I try to build my lessons on -- draw from what my learners already know.
  • 21. I start with METADATA MARC because they get it. So I try to teach linked data based on my learners’ interest in it. No surprise, for most of them, their interest has a lot to do with linked data replacing MARC. *CLICK* The rest of them are digital librarians and archivists, or aspiring digital librarians at any rate, and for them I keep library metadata practices in mind. *CLICK* So, for the sake of time, let’s just stick to MARC. What happens when I try to translate MARC skills and practices into a linked-data context?
  • 22. xlibber, “Bad Parking” CC-BY http://www.flickr.com/photos/xlibber/3870106899/ What happens is the same thing that happened with publishers and XML -- I crash my little linked-data car RIGHT INTO all the work that libraries now do, all the work that forms the FOUNDATIONS of library data, that is just IMPOSSIBLE to even DEMONSTRATE with linked data.
  • 23. I won’t tell you all my tales of woe -- I have a lot of them! -- but here’s one. I teach this continuing-education course that introduces XML and linked data to working librarians. This fall I wanted to add a couple of weeks on Open Refine to it. Because I thought that data cleanup was important to teach, for starters. And I thought that reconciling some random spreadsheet metadata with existing linked data stores would be a cool demo, with pretty obvious relevance to real-world librarian work. So naturally I thought about name authority control. Right?! Because it’s just so basic to what librarians do. Because it’s something the rest of the linked-data world is totally learning to do from libraries! Because even in the States -- where we’re kind of behind Europe in linked-data experimentation -- even in the States we have these great name authority linked-datastores, VIAF and the Library of Congress, so I thought this would be EASY.
  • 24. I learned very quickly, of course, that I can’t use VIAF from Open Refine, because there’s no SPARQL endpoint for it. And I’m on the record here, so I’ll just say -- YOU tell ME why not. So, okay, that doesn’t work, what about the Library of Congress? Naturally I went right to the source, Ed Summers, because who wouldn’t?
  • 25. Oops. Can’t do authority-control reconciliation THAT way either. And this is where I confess the limits of my own knowledge: I don’t KNOW how to build a web-available triplestore with a SPARQL endpoint off somebody else’s data! And this lesson I was working on was two weeks from going live -- I didn’t have time to figure it out!
  • 26. So I asked if anybody else had maybe done authority control with Open Refine and could show me how. I just needed a simple demo! I heard nothing.
  • 27. So let me just say, trying to put together a useful lesson about how to do ACTUAL LIBRARY WORK with linked data? Was NOT a super-humane experience. I felt annoyed. I felt stupid. I felt frustrated. I felt like hey, if the Semantic Web is so soylent, HOW ABOUT I JUST EAT UP ALL YOU LINKED DATA NERDS? And I am a vegetarian! Authority control is basic, basic stuff, folks. Many librarians consider it a touchstone of library practice, something CENTRAL to our professional identities. (So to speak.) If I can’t do authority control with linked data, do not even TALK to me about how linked data is more flexible, linked data is wonderful, linked data is superior -- linked data is USELESS. It is useless for librarians in practical terms. That’s not a problem with librarians. That’s a problem with linked data.
  • 28. The end of the story, just to add insult to injury, is that THIS happened. Though I was able to fix it, after some searching and fiddling. And that leads me to another thing I want to talk about, which is the state of tools available for just messing around with linked data.
  • 29. These are the instructions for installing the RDF extension for Open Refine -- which, by the way, I think this is great and I want more things like it. These are the LONG instructions, mind you -- there’s a shorter set on the main page. *CLICK* There’s a major error in these; you can’t actually get to the workspace directory from the Open Refine start page, because the start page starts on the Create tab, not the Open tab. I flatter myself I’m pretty tech-savvy, but I had to click around and swear a bit before I figured out what these instructions were getting at.
  • 30. So I wrote my own installation instructions, that seemed to work pretty well. You’re welcome. PLEASE don’t make me do this again. Wrong installation instructions are just NOT SOYLENT. And this installation method? Is ridiculous on its face. Not soylent at all. If there are better tools -- tools that help me... help my learners... get ACTUAL LIBRARY WORK DONE with linked data, I do not know what they are. I’m not sure they even EXIST. And that’s a gigantic problem for me as an educator, and ultimately it’s a gigantic problem for you and for linked data. If I fail at my job, you know what happens.
  • 31. XML IN PUBLISHING It’s what happened with XML and publishing, where XML did NOT HELP get publishing work done.
  • 32. INSTITUTIONAL REPOSITORIES IN ACADEME It’s what happened with institutional repositories, which basically didn’t help ANYBODY get any work done.
  • 33. Rob Boudon, “Jamie Lyon - YAY WOW” CC-BY http://www.flickr.com/photos/robboudon/6052727720/ Soylent technologies, technologies that are so respectful of people that people jump for joy about using them, HELP THOSE PEOPLE GET STUFF DONE. It’s as simple as that. And this needs to be true for people who are NOT linked data nerds and NOT programmers. Look, fundamentally, this is the same reason programmers hate MARC! MARC gets in the way of programmers getting useful work done, right? But if linked data puts every other librarian on earth in the position that library programmers are currently in? That’s not going to help linked-data adoption in libraries.
  • 34. NEGATIVE PATH DEPENDENCE Colby Stopa, “Path” CC-BY http://www.flickr.com/photos/photographybycolby/10169675563/ So to sum up here... because I can’t educate people well, and because the tools are so bad, and because practically nobody can actually get library work done with linked data, linked data is stuck *CLICK* in what I’ve seen called NEGATIVE PATH DEPENDENCE. What’s negative path dependence? I quote from a recent report on data sharing: “Because of high switching costs, inferior technologies can become so dominant that even superior technologies cannot surpass them in the marketplace.” Sounds like XML in publishing, right, compared to PDF? Sounds like institutional repositories against journals, right? I’m afraid it sounds like linked data against MARC, too. Meaning no disrespect at all to the great Henriette Avram, MARC is the inferior technology here! I really believe that! But linked data, despite its superiority, can’t get library work done at this point without ridiculous costs, so it can’t replace MARC. But. It doesn’t have to be this way. This I also believe.
  • 35. FOUR HCHALLENGES-WEB T SEM OYLEN ES FOR T So I’ll close with four challenges for the Soylent Semantic Web, the Semantic Web that is made of librarians and other people. I hope -- and I believe! -- that presenters at this conference will answer these challenges, and I look forward to seeing that... and I also hope that all of you take these challenges home and work on them.
  • 36. Challenge #1: WORK, NOT ONTOLOGIES for linked data Here is my linked-data heresy. Feel free to turn me into hamburger for it later: I don’t CARE about your ontology. I don’t care about ANYBODY’s ontology, or data model, or graph, or whatever. I. Do not. CARE. Why should I? We’ve done library work without ontologies and picture-perfect data models for hundreds of years. Somehow or other. Can we just get off ontologies already? What I care about? I care about the WORK I can do with linked data, and the work librarians can do with linked data, and the work my learners can do with linked data. I care about the tools that help them do that work. I care about the work skills I can realistically teach my learners that someone will pay them for -- and before you say anything, “knowing an ontology” is NOT something employers are gonna pay for! So I don’t need ontologies. I need well-documented linked-data tools that I can use and teach. I need linked-data workflows, based on real-world problems and real-world solutions, that I can demonstrate and imitate. I need linked-data systems that do REAL LIBRARY WORK, right out of the box. And very little of this exists today, because too much of the linked-data community is off in corners having arcane discussions about OWL same-as and H-TT-P range fourteen. Just like XML namespaces back in the day! And I’m saying, STOP THAT. Before you write ONE MORE LINE of OWL or R-D-F Schema, write code that lets real live people do real-world work with linked data.
  • 37. Challenge #2: IT’S ABOUT IT’SNOT ABOUT WHAT YOU CAN DO WHAT I CAN DO with linked data When I was running institutional repositories, I went to conferences about them, as ya do. And at those conferences I saw a LOT of demos of new and innovative software hacks. And a lot of those demos were absolutely amazing -- but they were completely irrelevant to me, because they were impossible to implement in my environment. So I challenge everyone here, because you are all experts already, to stop thinking about what YOU can do with linked data *CLICK* and instead think about what *I* can do with linked data. And what my learners can do. And what catalogers and metadata librarians and digital-library managers and institutional-repository managers and reference librarians can do! Because if YOU are the only one who can do what you do with linked data, librarianship writ large will NEVER be able to do it. And if you think this is a stealth demand for better tool usability, you’re absolutely right, it is! But that’s not all it is. This means that you need to learn about what I do, and what I CAN do. And what catalogers and metadata librarians and all the rest of us do, right? Maybe actually watching us do it? Maybe doing some of it yourselves? Yeah. So I challenge you to be curious about my work environment, as an educator. And catalogers’ work environments. And digital-library work environments. Find out about those, firsthand, and use what you learn to build linked-data systems that all librarians and libraries benefit from.
  • 38. Challenge #3: WOW WOW ME! LIBRARIANSHIP with linked data My third challenge, and I’m quite hopeful about this one, actually -- make me say WOW! about something you did with linked data. *CLICK* And why stop at me? I challenge you to wow all of librarianship with linked data!
  • 39. Some of you may remember the rollout of the Endeca-based library catalog at North Carolina State University in the mid-two-thousands. For those of you who don’t recall, it was this ONE CATALOG that started the whole discovery-layer movement. And what I remember most about that was that the new catalog got basically zero pushback from librarianship generally. Even though it was a HUGE change where you’d normally expect a lot of negative path dependence to kick in. Instead, everybody said WOW. Wow, I want that! Wow, look, facets for narrowing searches! Wow, check it out, you can actually start a query by drilling down through subject headings! Wow, de-duplicated records! Wow, relevance ranking! It was just a giant leap forward from what we had. Forget negative path dependence, people wanted this functionality NOW. I challenge you to make something for libraries with linked data that has as much wow as that original Endeca catalog did. So much wow that nobody even argues about linked data because everybody wants what it can do.
  • 40. Challenge #4: DISRUPT MARC with linked data Okay, I’m just gonna say this: If we want MARC dead? And we do! We’re gonna have to kill it ourselves and eat the evidence. But I have a different idea about how to do this than I think most librarians in the linked-data space do. I see linked-data effort focusing on big national libraries, big academic libraries, big consortia, nothing but bigbig-big. I’m not sure that’s the right strategy all by itself, to be honest. And I’m sorry for using the word “disrupt” because I know it’s a giant cliché now, but I’m serious about it. Let me explain what I mean.
  • 41. w.marsh, “old shelby park library” CC-BY http://www.flickr.com/photos/40943981@N00/3185725324/ Last summer I taught another continuing-education course for public librarians, about acquiring books from independent publishers and people who self-publish. And one of my learners, who is a public librarian in a smalltown public library like the one I’m showing here -- she said a very sad thing. There was NO WAY her library would be able to buy indie or self-published books, not print and not electronic. Just no way. Why not, I asked? Because there are only two employees at that library, she said, so they can’t do ANY original cataloging! That librarian and her little tiny two-person library? They’re what disruption theory calls an “underserved market.” MARC is no good for her -- it’s too complicated and too expensive. If you can make a simple linked-data system that’s cheaper and easier and more convenient for her, and lets her put in all the books she wants, including indie books, and lets her patrons find all the books they want, SHE WILL USE IT. And so will a LOT of little tiny libraries that just can’t do MARC. And if linked data is so easy and so great that little tiny libraries with two employees use it, what’s everybody else’s excuse, right? If linked data starts small, it can take over the world from MARC! I really believe this!
  • 42. Library linked data FOR GREA JUS T TICE So if you say linked data is so much better than MARC, I’m saying prove it, for great justice! Okay, okay, last nerd joke, I promise. But the serious point behind the joke is that there really is a social justice issue here! Linked data shouldn’t be something that only helps big libraries and their librarians. Let’s build small first, and build up from there, and then we can help ALL libraries, all librarians, and ALL library patrons. I think a linked-data catalog... that small libraries and their librarians can actually USE, and is demonstrably better than what they have... can be built. Right now, today, it can be built. I challenge you to build it, for great justice -including justice within librarianship for linked data.
  • 43. Vielen dank! Dorothea Salo salo@wisc.edu This presentation is available under a Creative Commons 3.0 Attribution United States license. Please respect CC licenses on photos if you reuse. So once again, thanks for having me, and I look forward to the rest of the conference!