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.

ODW13 Draft URI-strategy for NL PSI


Published on

Presentation with notes of considerations of the technical aspects of a URI-strategy for Public Sector Information in The Netherlands.

Published in: Technology, Business
  • Follow the link, new dating source: ❤❤❤ ❤❤❤
    Are you sure you want to  Yes  No
    Your message goes here
  • Sex in your area is here: ❤❤❤ ❤❤❤
    Are you sure you want to  Yes  No
    Your message goes here

ODW13 Draft URI-strategy for NL PSI

  1. 1. Concept URI Strategyfor the NL Public SectorDRAFT version – Q1 2013Hans Overbeek @hoverbeeThijs Brentjens @thijsbrentjens
  2. 2. Starting pointsDesigning URI Sets forthe UK Public Sector.D7.1.3 - Study on persistent URIs, with identification ofbest practices and recommendations on the topic for theMSs and the EC
  3. 3. URI-strategy: why?
  4. 4. URI-strategy: why?TrustIntuitionRecognizability
  5. 5. Goal of URI-strategy for PSIWhy is this important for Government information?•Indication that URI comes from trustworthy, authentic register.•Re-use of existing registers with authentic data•Re-use of existing harmonisation models•Making this ituitive, easy, attractiveInsight
  6. 6. Goal of URI-strategyModelDataReference-objectsa1b2c3c2c1a3a2b3b1Standard ApplicationAuthenticRegisterInsight
  7. 7. Re-use of Ontology TermsModelDataReference-objectsa1b2c3c2c1a3a2b3b1Standard ApplicationAuthenticRegisterInsight
  8. 8. Re-use of Reference ObjectsModelDataReference-objectsa1b2c3c2c1a3a2b3b1Standard ApplicationAuthenticRegisterInsight
  9. 9. Re-use of Reference ObjectsModelDataReference-objectsa1b2c3c2c1a3a2b3b1Standard ApplicationAuthenticRegisterInsighta3
  10. 10. No Register?No Identifier!Insight
  11. 11. URI paternTo encourage adoption:•KISS (human readable, short)•Trustworthy•Intuitive•Persistenthttp://{domain}/{type}/{concept}/{reference}Conclusion
  12. 12. http://{domain}/{type}/{concept}/{reference}{domain} identifies the register in a persistentwaySo idealy: {register}• {register}: No register, no identifier!• ‘’: recognisable, trustworthy, persistent.or: {sector}{register} ?• Which part DNS-adressable?or {yourdomain}/{yourpath} ?Ques-tions
  13. 13. http://{domain}/{type}/{concept}/{reference}{domain} = {register} infrastructure is needed?• A register of registers• Register name• Register mnemonic• Register resolver• Register administrator• How will apps use the resolvers and how frequently?Ques-tions
  14. 14. http://{domain}/{type}/{concept}/{reference}{type}• ‘id’: identifier of real life object *in a register*• ‘doc’: documentation about the real life object bythis register• ‘def’:Wait, let me…
  15. 15. http://{domain}/{type}#{concept}{type}• ‘def’: definition of a term in an ontology• Hash-URI• URI of model: http://{domain}/defUK-strategy recommends slash URI’s forvocabulary terms. Why?Sometimes no clear distinction between modeland contentQues-tions
  16. 16. http://{domain}/{type}/{concept}/{reference}{concept}• The {concept} is ‘just a string’ NOT the formalclassification of the identified resource. It has nosemantic meaning, just comes in handy for thehuman reader and helps to make uniquereferences• Singular• Avoid all other characters than a-z, A-Z, 0-9• CamelCase or lowercase? Ques-tions
  17. 17. To identify concepts:• Classes, properties and skos:concepts• Hash-URI always retuns complete ontologyhttp://{domein}/def• Use UpperCamelCase for classes andconcepts, lowerCamelCase for propertieshttp://{domain}/def#{concept}
  18. 18. http://{domain}/{type}/{concept}/{reference}{reference}Key of the resource within the register. URI-strategyleaves lot of freedom to the registrar: many differentrequirementsSome recommendations:•Try to avoid special characters•Use W3CDTF for versions•Avoid information bearing keys