accessible
play

Accessible #FAIR101 #ARDCtraining Webinar 3 PRESENTED BY Matthias - PowerPoint PPT Presentation

Accessible #FAIR101 #ARDCtraining Webinar 3 PRESENTED BY Matthias Liffers Code of Conduct To ensure that everyone has a fulfilling learning opportunity, FAIR Data 101 is governed by a Code of Conduct. You can view the Code at


  1. Accessible #FAIR101 #ARDCtraining Webinar 3 PRESENTED BY Matthias Liffers

  2. Code of Conduct To ensure that everyone has a fulfilling learning opportunity, FAIR Data 101 is governed by a Code of Conduct. You can view the Code at tiny.cc/code-conduct If you observe a breach of the Code of Conduct, please contact us using the form linked in the Code. 2

  3. Today’s agenda ● Accessible ○ A1, A1.1, A1.2 ● Machine accessibility ● Protocols and their layers ● Examples of protocols working together 3

  4. Now we know where it is - how do we get to it? 4

  5. A1 (meta)data are retrievable by their identifier using a standardised communications protocol . A1.1 the protocol is open, free, and universally implementable . A1.2 the protocol allows for an authentication and authorisation procedure , where necessary.

  6. Why do we care about machine accessibility? 6

  7. 7

  8. 8

  9. 9

  10. /ˈpɹəʊtəˌkɒl/ https://en.wiktionary.org/wiki/protocol 10

  11. an accepted code of conduct; acceptable behaviour in a given situation or group https://en.wiktionary.org/wiki/protocol 11

  12. a set of formal rules describing how to transmit or exchange data, especially across a network https://en.wiktionary.org/wiki/protocol 12

  13. Standard Open Free Universally Implementable

  14. Why?

  15. Trust 15

  16. Identifying standards with standard identifiers

  17. TCP/UDP/IP 10.17487/RFC1122 HTTP 10.17487/RFC2068 IP over Avian Carriers 10.17487/RFC2549 Ethernet IEEE 802.3 Wifi IEEE 802.11 MQTT mqtt- v3.1.1 (well…) XML http://www.w3.org/TR/2008/REC-xml-20081126/ JSON 10.17487/RFC8259 17

  18. https://tools.ietf.org/html/rfc2549

  19. Protocols are like ogres 19

  20. 20 Jsoon eu CC BY-SA

  21. 21 Mark Torrada CC BY, Ben Davis CC BY, Yoyon Pujiyono CC BY, Wilson Joseph CC BY, Stan Fisher CC BY, Jsoon eu CC BY-SA

  22. We only care about the very top layer(s) 22

  23. (Mostly) 23

  24. Examples

  25. Two repositories can use OAI-PMH to share Dublin Core metadata as XML over HTTP 25

  26. https://oai.prosecutionproject.griffith.edu.au/oai?verb=ListRecords&metadataPrefix=oai_dc 26

  27. https://oai.prosecutionproject.griffith.edu.au/oai?verb=ListRecords&metadataPrefix=oai_dc 27

  28. https://oai.prosecutionproject.griffith.edu.au/oai?verb=ListRecords&metadataPrefix=oai_dc 28

  29. https://oai.prosecutionproject.griffith.edu.au/oai?verb=ListRecords&metadataPrefix=oai_dc 29

  30. https://oai.prosecutionproject.griffith.edu.au/oai?verb=ListRecords&metadataPrefix=oai_dc 30

  31. https://oai.prosecutionproject.griffith.edu.au/oai?verb=ListRecords&metadataPrefix=oai_dc 31

  32. 32

  33. A sensor network can transmit MySensors data as JSON over MQTT 33

  34. Infinite diversity in infinite combinations

  35. There is no one repository to rule them all

  36. Infrastructure literacy 36

  37. Data and metadata do not need to be colocated!

  38. A1.2 the protocol allows for an authentication and authorisation procedure , where necessary.

  39. Authorisation and access

  40. Username/password 40

  41. API key 41

  42. Infrastructure and policy 42

  43. What’s next? Accessible part 2 with Liz Stokes ● Wednesday 12:00 AWST / 13:30 ACST / 14:00 AEST 43

  44. CONTACT +61 418 933 678 matthias.liffers@ardc.edu.au ardc.edu.au

Recommend


More recommend