The document discusses the work of the International Image Interoperability Framework (IIIF) Technical Working Group on discovery of IIIF resources. It outlines four areas of work: crawling and harvesting IIIF resources, accessing semantic descriptive content for indexing, synchronization between publishers and aggregators, and importing resources into viewers. It then evaluates options for harvesting IIIF resources, including using IIIF collections, sitemaps, ResourceSync, HTTP extensions, Schema.org, and ActivityStreams. It notes ongoing work to draft an import specification based on hackathon implementations. The document concludes with proposed discussion topics for the meeting.

1. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Discovery
of
IIIF
Resources
International
Image
Interoperability
Framework
Technical
Working
Group
Vatican,
June
2017

2. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Discovery
Areas
of
Work
Four
areas
of
work
will
facilitate:
1. crawling
and
harvesting
of
IIIF
resources
2. access
to
semantic
descriptive
content
for
indexing
3. synchronization between
publisher/aggregator
4. import
to
viewers once
the
resource
is
found
Charter:
• http://iiif.io/community/groups/discovery/charter/

3. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Chartered
Timeline
• Q4
2016:
Group
established,
work
commences
• Q1
2017:
Gather
Use
Cases;
Publish
Import
draft
• Q2
2017:
Publish
Crawling
draft
• Q3
2017:
Publish
Indexing
and
Notification
drafts
• Q4
2017:
Revisions
to
Import;
Implementations
of
Crawling
• Q1
2018:
Implementations
of
Indexing
and
Notification
• Q2
2018:
Revisions
to
specifications
and
implementations
• Q3
2018:
Revisions
to
specifications
and
implementations

4. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Chartered
Timeline
• Q4
2016:
Group
established,
work
commences
• Q1
2017:
Gather
Use
Cases;
Publish
Import
draft
• Q2
2017:
Publish
Crawling
draft
• Q3
2017:
Publish
Indexing
and
Notification
drafts
• Q4
2017:
Revisions
to
Import;
Implementations
of
Crawling
• Q1
2018:
Implementations
of
Indexing
and
Notification
• Q2
2018:
Revisions
to
specifications
and
implementations
• Q3
2018:
Revisions
to
specifications
and
implementations

5. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Harvesting
Discussions:
Options
• IIIF
Collections
• Sitemaps
• With
ResourceSync
• With
IIIF
Extensions
• With
HTTP
layer
Extensions
• Schema.org
• ActivityStreams 2.0

6. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Harvesting:
Collections
ü Already
part
of
the
specification,
nothing
new
to
do
ü Ensures
finding
IIIF
Resources
❌ Different
usage
– curation/presentation
vs
discovery
❌ Will
find
same
content
multiple
times
❌ Slow,
inconsistent
implementations
❌ No
incremental
update
support
or
document
metadata
❌ Not
sure
if
people
create
top
level
collections
• Mitigation:
Clear
discovery
profile
for
collections?

7. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Harvesting:
Sitemaps
ü Understood
by
web
search
engines
(useful?)
ü Simple
spec,
lots
of
implementations
❌ Conflict
with
CMS
sitemaps
❌ Difficult
to
reproduce
set
membership
vs
entire
collection
• Mitigation:
Separate
IIIF
sitemap
hierarchy?
❌ Duplicates
collection
information
❌ XML
not
JSON
❌ Not
Linked
Data

8. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Harvesting:
+ResourceSync
ü +
hierarchical
sets,
dump
files,
changelogs,
metadata
ü +
seeAlso in
ResourceSync file
directly
ü Notifications
pattern
(callbacks+websub)
❌ Makes
simple
spec
complex
– quite
far
from
Sitemaps
❌ With
all
of
its
challenges
still
❌ Lack
of
implementations
/
adoption

9. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Harvesting:
+Other
Extension
ü Add
only
necessary
features
in
own
namespace
ü Smaller
spec
than
ResourceSync
❌ But
not
a
standard,
and
would
compete
Other?

10. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Harvesting:
+HTTP
ü Use
only
standards
ü Separates
document
metadata
and
object
metadata
❌ Difficult
to
implement
for
both
client
and
server
Other?

11. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Harvesting:
Schema.org
ü ???
❌ ???
Not
yet
discussed

12. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Harvesting:
ActivityStreams
ü ???
❌ ???
Not
yet
discussed

13. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Import
to
Viewers
Ongoing
work
to
draft
a
specification
based
on
hackathon
implementations.
Call
for
use
cases
closed:
https://github.com/IIIF/iiif-­‐stories/
issues?q=is%3Aissue+is%3Aopen+label%3Adiscovery-­‐import

14. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Discussion
Topics
Discuss
and
evaluate
use
cases
Discuss
scope
of
work
Continue
technical
discussion
of
formats
(if
time)

15. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Discuss!