The document discusses updates and improvements to the IIIF Shared Canvas framework, emphasizing the need for synchronization between APIs and the underlying model. Key proposals include simplifying the model, adding new concepts for audio-visual content, and clarifying definitions and interactions. Additionally, it recommends deferring the implementation of 3D concepts until further experience is gathered.

1. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Shared
Canvas
2.0
International
Image
Interoperability
Framework

2. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Shared
Canvas?
• RDF
Model
that
the
Presentation
API
is
built
from
• Source
of
those
“sc:”
prefixes!
• Predates
IIIF
Focus
has
been
on
the
APIs,
not
the
model,
towards
ease
of
interoperability.

3. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Shared
Canvas
2.0
• APIs
have
advanced
beyond
the
model
• Need
to
get
them
back
in
sync
• New
APIs
require
updates
to
the
model
• e.g.
A/V
needs
a
“time”
dimension
for
a
Canvas
• Model’s
referenced
ontologies
have
been
updated
• e.g.
OAC
à OA
à WAWG
• Or
we
no
longer
use
them
• e.g.
OAI-­‐ORE

4. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Resynchronize
Update
the
model
from
the
Presentation
API
• Drop
ORE
in
favor
of
rdf Lists
• Add
classes,
no
Collections
even!
• Add
new
concepts
like
viewingHint,
viewingDirection
• Add
new
relationships
like
contentLayer,
members
• Update
documentation
to
be
in
sync
with
Prezi
• Provides
the
theoretical
background
to
understanding
the
API

5. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Update
Update
the
model
for
new
Standards
• JSON-­‐LD
as
target
serialization
• Use
Web
Annotation
WG
model,
not
older
OA
• Incorporate
ActivityStreams (paging)
• Drops
AnnotationList,
Layer
• Consider
interactions
with
REST
• LDP
Containers?

6. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Simplify
Make
it
simpler:
• Drop
Zones
in
favor
of
nesting
Canvas
• Rotation
done
in
Annotation
• New
use
cases
in
AV
of
audio
only
canvases
• Incorporate
Presentation
API
optimizations
• e.g.
other_content vs
images

7. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Clarify
Make
the
model
clearer:
• What
is
a
“service”?
• Interactions
between
Range
and
Sequence?
• Do
we
need
a
protocol
or
profiles?
• Extract
Annotation
use
cases
to
separate
documents?

8. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Extend
Add
concepts
needed
for
A/V:
• Add
Duration
to
the
Canvas
• Make
height/width
non-­‐mandatory
• Transitions
between
canvases
More
specific
motivations?
• Transcribing
vs
Translating

9. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Extend

10. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Extend

11. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Defer
Do
not
yet
add
concepts
for
3D:
• 3D
space
is
unbounded,
canvases
are
bounded
• 0,0
is
upper
left
corner
• 0,0,0
is
point
in
the
center
• Not
enough
experience
• Don’t
want
to
reinvent
VRML!

12. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Defer
Do
not
yet
add
concepts
for
3D:
• Don’t
want
to
reinvent
VRML!
• Or
X3D
• Or
WebGL
• Or
WebVR
• Or
CSS3D
• Or
…

13. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Shared
Canvas
@azaroth42
rsanderson
@getty.edu
Discuss!