@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Publishing	&	Retrieving
Linked	Open	Usable Data	
Rob	Sanderson
Semantic	Architect
J.	Paul	Getty	Trust
rsanderson@getty.edu
@azaroth42
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Attention	to	Publishing	&	Retrieving
Ontologies
RDF
All	Five	LOD	Stars!
LDP
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
We	Built	It	… Where	Are	They?
https://www.flickr.com/photos/105458023@N02/10287818523/
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
They’re	Where	Everyone	Else	Is
https://www.flickr.com/photos/jonathangrossphotography/17204367619/
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
RDF:	Not	In	My	Backyard
Image	By	Z22	- https://commons.wikimedia.org/w/index.php?curid=30929934Title:	http://manu.sporny.org/2012/nuclear-rdf/
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
LOUD:	Linked	Open	Usable Data
• Just	Use	Federated	SPARQL	Queries
• Data	Models	and	Ontologies	make	bad	APIs
• APIs	are	the	UIs	of	Developers,	and	need:
⭐ Correct	Abstraction level	for	the	Audience
⭐ Few	Barriers to	Entry	
⭐ Comprehensible by	introspection
⭐ Thorough	Documentation with	copy-able	examples
⭐ Few	Exceptions,	instead	consistent	patterns
• Conflict	between	completeness,	precision	&	usability…
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Patrick	Hochstenbach,	@hochstenbach
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Patrick	Hochstenbach,	@hochstenbach
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Usable vs	Complete
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Target	Zone
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Incremental	Complexity
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Incremental	Complexity
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Incremental	Complexity
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
What	to	do?
⭐ Solve	actual	challenges,	documented	as	use	cases
• Using	data	that	is	captured	and	available
• That	meet	institutional	norms	and	requirements
⭐ Describe	shared	domain	use	cases	consistently
• While	allowing	local	extensions	for	local	problems
⭐ Ensure	data	can	be	productively	used	
• Via	easy-to-implement	&	maintain	services
• With	various	easy-to-implement	applications	
⭐ Design	for	reuse	by	others.
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
JSON-LD:	{}s	are	the	new	<>s
⭐ Speak	to	your	audience	in	their	language!
• 10%	- 19%	of	all	websites	have	JSON-LD	data
xml	api json api
(Feb	2018)	https://w3techs.com/technologies/details/da-jsonld/all/all
(Nov	2017)	http://webdatacommons.org/structureddata/2017-12/stats/stats.html
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Data	Model	and	API?	
JSON-LD	contexts	and	frames	abstract	the	representation	
from	the	ontology,	providing	the	necessary	separation	of	
concerns	between	data	model	and	API	to	enable	usability	
without	compromising	on	semantics.
@azaroth42
rsanderson
@getty.edu
IIIF:	Interoperabilituy
Linked	Open	
Usable	Data
@azaroth42
rsanderson
@getty.edu
Thank	You!
Rob	Sanderson
rsanderson@getty.edu
@azaroth42

Publishing Linked Open Usable Data