Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

EuropeanaTech Keynote: Shout it out LOUD

1 181 vues

Publié le

Linked Open Data is great for recommendations about publishing data, but we need five more stars for the consumer -- How can it be both complete and usable? Design principles for Linked Open Usable Data.

Publié dans : Technologie
  • Soyez le premier à commenter

EuropeanaTech Keynote: Shout it out LOUD

  1. 1. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Shout it Out: LOUD Rob Sanderson Semantic Architect J. Paul Getty Trust rsanderson@getty.edu @azaroth42
  2. 2. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu The Semantic Web http://rubenverborgh.github.io/WebFundamentals/ birds-eye-view/images/scientific-american.jpg
  3. 3. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu The (Imagined) Semantic Web But not how they thought it would
  4. 4. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Linked Open Data http://5stardata.info/en/
  5. 5. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu (Publishing) Linked Open Data ?
  6. 6. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Linked Open Data
  7. 7. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Usable Linked Open Data
  8. 8. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Usable? … usability is the degree to which [a thing] can be used by specified consumers to achieve [their] quantified objectives with effectiveness, efficiency, and satisfaction in a quantified context of use. who what how where Usability is dependent on the Audience https://en.wikipedia.org/wiki/usability “ ”
  9. 9. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Who? With thanks to Patrick Hochstenbach, @hochstenbach
  10. 10. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu 2 LOD … Profit!
  11. 11. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Developers!
  12. 12. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu What? How? Where? 1. Know Your Audience 2. Meet on Their Terms 3. Have a Conversation 4. Create Opportunities for Meaningful Participation /ht Catherine Bracy, @cbracy
  13. 13. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Usability 1. Know Your Audience 2. Meet on Their Terms 3. Have a Conversation 4. Create Opportunities for Meaningful Participation
  14. 14. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu The API is the Developers’ User Interface When it comes to APIs, developers are your users. The same principles of user- centred-design apply to the development and publication of APIs (simplicity, obviousness, fit-for-purpose etc) http://apiguide.readthedocs.io/en/latest/principles/empathy.html “ ”
  15. 15. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu What is the API for LOD? Provide useful information about what a name identifies when it's looked up, using open standards such as RDF, SPARQL, etc. In LOD, the ontology determines the API This is not meeting on the audience’s terms “ ” -- TimBL
  16. 16. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu
  17. 17. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Usable (API) vs Complete (Model)
  18. 18. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Target Zone
  19. 19. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Incremental Complexity
  20. 20. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Incremental Complexity
  21. 21. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Incremental Complexity
  22. 22. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Five Stars of Linked Open Usable Data ⭐ right Abstraction for the audience ⭐ few Barriers to entry ⭐ Comprehensible by introspection ⭐ Documentation with working examples ⭐ few Exceptions, many consistent patterns
  23. 23. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu A is for the right Abstraction https://www.flickr.com/photos/emilgh/2801393221/
  24. 24. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu A is for the right Abstraction
  25. 25. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu A is for the right Abstraction https://www.flickr.com/photos/markmorgantrinidad/14860681369/ https://www.flickr.com/photos/57293605@N07/14345959147/
  26. 26. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu B is for few Barriers to Entry https://www.flickr.com/photos/tfpc/6112503326/
  27. 27. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu C is for Comprehensible { "@context": "https://linked.art/ns/v1/linked-art.json", "id": "https://example.museum/data/object/1", "type": "ManMadeObject", "identified_by": { "type": "Name", "value": "Example Painting” }, "made_of": { "id": "aat:300015045", "type": "Material", "label": "watercolor" } }
  28. 28. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu D is for Documentation https://www.w3.org/TR/annotation-model/
  29. 29. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu E is for few Exceptions M.C. Escher, Two Birds (No. 18)
  30. 30. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu E is for few Exceptions
  31. 31. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Examples? https://linked.art/
  32. 32. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Five Core Design Principles 1. Require Use Cases, with Data 2. As Simple as Possible 3. Don’t Break the Web 4. Define Success, Not Failure 5. Design for JSON-LD, Consistently
  33. 33. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Require Use Cases, with Data! Uses Cases, supported by data, keep LOD grounded in reality and help find the correct abstraction
  34. 34. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu As Simple as Possible Image source: Alamy
  35. 35. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Don’t Break the Web https://www.flickr.com/photos/patchattack/10784011155/
  36. 36. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Define Success, Not Failure https://en.wikipedia.org/wiki/Jon_Postel
  37. 37. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Design for JSON-LD, Consistently 10% - 20% of all websites have JSON-LD data (schema.org) json api xml api https://trends.google.com/trends/explore?date=all&q=json%20api,xml%20api (Feb 2018) https://w3techs.com/technologies/details/da-jsonld/all/all (Nov 2017) http://webdatacommons.org/structureddata/2017-12/stats/stats.html
  38. 38. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @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/
  39. 39. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu JSON-LD 1.1 https://json-ld.github.io/charter/
  40. 40. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Insights to Take Away ⭐ right Abstraction ⭐ few Barriers ⭐ Comprehensible ⭐ Documentation ⭐ few Exceptions ⭐ Require Use Cases ⭐ Simple as Possible ⭐ Don’t Break the Web ⭐ Define Success ⭐ Consistent JSON-LD Ensure Your Data is LOUD
  41. 41. @azaroth42 rsanderson @getty.edu IIIF:Interoperabilituy LinkedOpen UsableData @azaroth42 rsanderson @getty.edu Thank You! Rob Sanderson rsanderson@getty.edu @azaroth42

×