IIIF: Shared Canvas 2.0

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@getty.edu

Shared  Canvas  2.0

InternationalImageInteroperabilityFramework

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@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.

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@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

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@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

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@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?

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@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

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@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?

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@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

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@getty.edu

Extend

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@getty.edu

Extend

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@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!

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@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  …

@azaroth42

rsanderson@getty.edu

IIIF:  Interope

rabilituy

IIIF:  Shared  Ca

nvas

@azaroth42rsanderson@getty.edu

Discuss!