Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

IIIF and Linked Data: A Cultural Heritage DAM Ecosystem

619 views

Published on

Presentation at DAMLA, November 15 2017, on the adoption of the IIIF image interoperability APIs across the Cultural Heritage sector for access to digital assets. How Linked Open Data then provides interoperable discovery solutions for that content.

Published in: Technology
  • Be the first to comment

IIIF and Linked Data: A Cultural Heritage DAM Ecosystem

  1. 1. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu IIIF  and  Linked  Data A  Cultural  Heritage  DAM  Ecosystem Rob  Sanderson Semantic  Architect J.  Paul  Getty  Trust rsanderson@getty.edu,  @azaroth42 http://iiif.io/    http://linked.art/
  2. 2. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Images  are  Core  Information  Carriers
  3. 3. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Yet,  we  heard  …
  4. 4. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu I  am  locked  into   my  image   delivery  software
  5. 5. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu (on  mobile) My  users  want   deep  zoom (on  mobile)
  6. 6. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu They  want  to  compare  objects…
  7. 7. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu I  want  to   compare  objects They  want  to  compare  objects across  organizational  boundaries
  8. 8. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu They  want  to  annotate my  images…
  9. 9. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu …  but  I  don’t  want  to  lose  control
  10. 10. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Oh,  and  …
  11. 11. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu I  don’t  want  to  invent  any  of  it
  12. 12. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu http://iiif.io/
  13. 13. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu A  Community that  develops APIs, implements  them  in  Software,   and  exposes  interoperable  Content
  14. 14. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Some  of  the  IIIF  Community • Austria • British  Library • Cuba • Denmark • Egypt • France • Israel • Japan • Brown • Cambridge • Columbia • Cornell • Ghent • Harvard • Hong  Kong • Johns  Hopkins • Norway • Poland • Scotland • Qatar   • Serbia • Lib.  of  Congress • Vatican • Wales • Kyoto • Oxford • MIT • Princeton • Stanford • Tokyo • Toronto • Yale National  Libraries Universities
  15. 15. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu More  of  the  IIIF  Community • ArtStor • Axiell • CogApp • Digirati • Ex  Libris Group • Gallery  Systems • Internet  Archive • Klokan Tech. • Art  Gallery  of  Ontario • Art  Institute  of  Chicago • British  Museum • Carnegie  Museum  of  Art • Cooper-­‐Hewitt • Europeana Foundation • Frick  Collection • Indianapolis  Art  Museum • J.  Paul  Getty  Trust • Metropolitan  Museum  of  Art • National  Gallery  of  Art  (US) • National  Museum  of  Sweden • National  Gallery  of  Denmark • San  Francisco  MOMA • Walters  Art  Gallery • Yale  Centre  for  British  Art • Luna  Imaging • NetX • OCLC • Sirma Group • Synaptica • Text  &  Bytes • Wikimedia • Zegami Companies Museums  &  Galleries Plus  many  more!
  16. 16. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu APIs:  Agreement  Preceding  Interaction* Presentation Search Image Authentication (*  API  is  really:  Application  Programming  Interface)  
  17. 17. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu APIs  help  DAM  Managers • Affordable • Faster,  easier  and  better  than  single  system  solution   • Costs  are  shared  by  community,  including  design/docs • Flexible • Always  have  best  of  class  product • Ease  of  integration  with  existing  systems • Same  content  can  enable  many  applications Affordable  +  Flexible  =  Sustainable
  18. 18. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu APIs  help  DAM  Developers • Encourages  Innovation • Start  from  existing  design  &  code,  focus  on  added  value   • Shared  innovations  added  to  new  API  versions • Provides  a  Marketplace • Hundreds  of  organizations  in  need  of  solutions • Faster  development  =  cheaper  development   • Ease  of  integration  with  existing  products Innovation  +  Marketplace  =  Profit
  19. 19. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Successful  APIs  … • Solve  actual  challenges,  documented  as  use  cases • Using  data  that  is  captured  and  available • Allow  consistent  implementation  of  shared  use  cases • Allow  for  addition  of  further  functionality • Can  be  productively  used   • Via  easy-­‐to-­‐implement  services • With  easy-­‐to-­‐implement  applications • Provide  interoperability with  other  data  and  systems • Are  clearly  documented  with  relevant  examples
  20. 20. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Successful  APIs  … Are  developed  … • Iteratively • We  build  upon  success  and  learn  from  failure • Responsively • We  adapt  in  response  to  feedback • Responsibly • We  consider  changes/features  carefully • Collaboratively • We  engage  with  the  community  and  stakeholders
  21. 21. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu IIIF  Image  API http://iiif.io/api/image/ URL  pattern  to  access  pixels  and  technical  information
  22. 22. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu IIIF  Presentation  API Just  enough  structure  &  description  data  to  drive  a  viewer
  23. 23. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu AoE with  highlights http://iiif.io/api/presentation/
  24. 24. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Developer-­‐Friendly  Format { "@context":"http://iiif.io/api/presentation/3/context.json", "id": "http://example.org/iiif/manifest/1", "type": "Manifest", "label": {"en": "The Abduction of Europa (1632)"}, "metadata": [{ "label": {"en": "Artist / Maker"}, "value": {"en": "Rembrandt Harmensz. van Rijn"}}], "items": [ … ] } Easy  to  produce  and  consume  JSON  format  for  all  APIs
  25. 25. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu We  Heard  Feedback  … • Heh,  I  don’t  want  to  lose  control,  remember! • IIIF  Authentication  API guides  user  to  login • I  don’t  want  to  read  all  those  words! • IIIF  Search  API  enables  text  search  within  an  object • What  about  our  video  and  audio  content? • Next  Presentation  API  will  enable  time-­‐based  media • How  do  I  find  IIIF  resources  I’m  interested  in? • Working  on  object  discovery… • …  but  needs  semantic  metadata
  26. 26. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Linked  Art https://linked.art/ (Still  early  beta!)
  27. 27. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Linked.Art:  A  Cultural  Heritage  API Linked.Art provides  APIs  that  enable   cultural  heritage  institutions  to  easily  publish   their  data  for  use  by  digital  research  projects   and  by  non-­‐specialist  developers. 90%  of  the  use  cases  of   90%  of  the  organizations,  with 10%  of  the  complexity
  28. 28. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Successful  APIs… Focus on  the  primary  resources  of  concern  for  the  domain Core  Classes: • Object • Activity • Person • Place • Time
  29. 29. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Usable vs  Complete
  30. 30. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Target  Zone  for  Scope
  31. 31. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Incremental  Complexity
  32. 32. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Same  Developer-­‐Friendly  Format { "@context": "https://lod.museum/ns/context/1/full.jsonld", "id": "https://lod.museum/example/object/1", "type": "ManMadeObject", "classified_as": "aat:300033618", "label": "Example Painting", "made_of": { "id": "aat:300015045", "type": "Material", "label": "watercolor" } }
  33. 33. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu I  Thought  You  Said  Linked  Data?! IIIF  &  Linked.Art APIs  use  Linked  Data  throughout! • Emphasis  is  on  Linked  Open  Usable Data:  LOUD • JSON-­‐LD  format  looks  just  like  JSON   • No  need  for  complex  Semantic  Web  technologies! • Target  audience  is  every  developer 100%  Buzzword  Compliant;  Only  10%  of  the  Effort!
  34. 34. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu IIIF  &  Linked.Art:  A  DAM  Ecosystem • LOUD:  Linked  Open  Usable Data • IIIF gives  easy  access  to  content • Linked.Art gives  easy  access  to  metadata • Easy  to  implement  ;  easy  to  build  on  top  of • In  production  at  many  organizations • Massive  international  community,   many  in  need  of  solutions
  35. 35. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Thank  You! Rob  Sanderson rsanderson@getty.edu @azaroth42
  36. 36. @azaroth42 rsanderson @getty.edu IIIF:  Interoperabilituy IIIF  and  Linked  Data: A  DAM  Ecosystem @azaroth42 rsanderson @getty.edu Discuss!

×