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.

Dutch Government Business Case

1,746 views

Published on

Canned presentation about the application of the Dublin Core standard to the Dutch Government metadata standard OWMS. A business case presentation at DC-2009 in Seoul, Korea.

Published in: Technology, Education, Business
  • For information : I allowed myself to publish your excellent presentation on my blog HARDY’S CORNER (http://hardys-corner.blogspot.com/2011/05/dutch-government-business-case-view.html) Thanks for sharing and congratulations .Greetings from France. Have a nice weekend. Bernard

    (1)As part of the function Slideshare 'Embed Share on Blogger' or the function 'Embed '
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Dutch Government Business Case

  1. 1. Dutch Government Metadata O verheid.nl W eb M etadata S tandaard: OWMS Hans Overbeek [email_address] DC2009
  2. 2. Interoperability of government information <ul><li>1200+ organisations </li></ul><ul><li>1600+ websites
  3. 3. 16M+ citizens </li></ul>
  4. 4. Information Architecture Findability Any question Information (Content)
  5. 5. Information Architecture Findability Any question Information (Content) amsterdam.nl government.nl government.nl xyz.nl Any website
  6. 6. Information Architecture Findability Any question Information (Content) Location (e.g. map) Life event Theme Search term Structure of demand (Standard question) amsterdam.nl government.nl government.nl xyz.nl Any website
  7. 7. Information Architecture Findability Any question Information (Content) Location (e.g. map) Life event Theme Search term Structure of demand (Standard question) identifier title type language creator modified spatial temporal Metadata (“Dutch Core”) amsterdam.nl government.nl government.nl xyz.nl Any website
  8. 8. Information Architecture Findability Any question Information (Content) Location (e.g. map) Life event Theme Search term Structure of demand (Standard question) identifier title type language creator modified spatial temporal Metadata (“Dutch Core”) Knowledge model (Linked Data) Geo Subject Language amsterdam.nl government.nl government.nl xyz.nl Any website
  9. 9. Metadata: Dutch Government Core <ul><li>dcterms:identifier </li></ul><ul><li>dcterms:title
  10. 10. dcterms:type
  11. 11. dcterms:language
  12. 12. dcterms:creator
  13. 13. dcterms:modified
  14. 14. (dcterms:temporal)
  15. 15. (dcterms:spatial) </li></ul>8 properties mandatory (if applicable)
  16. 16. Aim: Simple content metadata Text Value from a VES URI URI with optional VES and Text <dcterms:title> Amsterdam.nl Homepage </dcterms:title>
  17. 17. Aim: Simple content metadata Text Value from a VES URI URI with optional VES and Text <dcterms:title> Amsterdam.nl Homepage </dcterms:title> <dcterms:spatial scheme=”overheid:Gemeente”> Amsterdam </dcterms:spatial>
  18. 18. Aim: Simple content metadata Text Value from a VES URI URI with optional VES and Text <dcterms:title> Amsterdam.nl Homepage </dcterms:title> <dcterms:spatial scheme=”overheid:Gemeente”> Amsterdam </dcterms:spatial> <dcterms:spatial resourceIdentifier=”http://standaarden.overheid.nl/owms/terms/Amsterdam” > </dcterms:spatial>
  19. 19. Aim: Simple content metadata Text Value from a VES URI URI with optional VES and Text <dcterms:title> Amsterdam.nl Homepage </dcterms:title> <dcterms:spatial scheme=”overheid:Gemeente”> Amsterdam </dcterms:spatial> <dcterms:spatial resourceIdentifier=”http://standaarden.overheid.nl/owms/terms/Amsterdam” > </dcterms:spatial> <dcterms:spatial scheme=”overheid:Gemeente” resourceIdentifier=”http://standaarden.overheid.nl/owms/terms/Amsterdam” > Amsterdam </dcterms:spatial>
  20. 20. Documentation of the standard Human readable documentation of the standard: http://tinyurl.com/nlgov-doc <ul><li>Eigenschappen = Properties
  21. 21. Waardelijsten = List of values (VES)
  22. 22. Toepassingen (IPM) = Application Profile
  23. 23. Overheid = Government </li></ul>
  24. 24. Metadata standard <ul><li>Dublin Core abstract model
  25. 25. Simple OWMS model
  26. 26. Collection application profile </li></ul>
  27. 27. Dutch abstract model
  28. 28. Description Set Profile in XSD http://tinyurl.com/nlgov-xsd
  29. 29. URI's: pointers to knowledge objects <ul><li>Knowledge Objects are defined resources within the overheid namespace
  30. 30. Every KO belongs to at least 1 owl:Class
  31. 31. Some KO's are skos:Concepts in a skos:ConceptScheme
  32. 32. Classes, ConceptSchemes and KO's share the same namespace
  33. 33. Nameing conflicts solved by qualification (like DBpedia: e.g. “http://dbpedia.org/resource/Paris” and “http://dbpedia.org/resource/Paris,_Texas_(film)”)
  34. 34. Linked Data tutorial at http://tinyurl.com/berlin-tut </li></ul>
  35. 35. Knowledge domains <ul><li>Geo
  36. 36. Organization
  37. 37. Information type
  38. 38. Subject
  39. 39. Language </li></ul>5. 4. 3. 2. 1.
  40. 40. Knowledge domains <ul><li>Geo
  41. 41. Organization
  42. 42. Information type
  43. 43. Subject
  44. 44. Language </li></ul>5. 4. 3. 2. 1.
  45. 45. Knowledge domains <ul><li>Geo
  46. 46. Organization
  47. 47. Information type
  48. 48. Subject
  49. 49. Language </li></ul>5. 4. 3. 2. 1. buy
  50. 50. Knowledge domains <ul><li>Geo
  51. 51. Organization
  52. 52. Information type
  53. 53. Subject
  54. 54. Language </li></ul>5. 4. 3. 2. 1. buy
  55. 55. Knowledge domains <ul><li>Geo
  56. 56. Organization
  57. 57. Information type
  58. 58. Subject
  59. 59. Language </li></ul>5. 4. 3. 2. 1. owl buy
  60. 60. Knowledge domains <ul><li>Geo
  61. 61. Organization
  62. 62. Information type
  63. 63. Subject
  64. 64. Language </li></ul>5. 4. 3. 2. 1. owl buy
  65. 65. Knowledge domains <ul><li>Geo
  66. 66. Organization
  67. 67. Information type
  68. 68. Subject
  69. 69. Language </li></ul>5. 4. 3. 2. 1. owl buy
  70. 70. Knowledge domains <ul><li>Geo
  71. 71. Organization
  72. 72. Information type
  73. 73. Subject
  74. 74. Language </li></ul>5. 4. 3. 2. 1. owl buy
  75. 75. Knowledge domains <ul><li>Geo
  76. 76. Organization
  77. 77. Information type
  78. 78. Subject
  79. 79. Language </li></ul>5. 4. 3. 2. 1. skos owl buy
  80. 80. Knowledge domains <ul><li>Geo
  81. 81. Organization
  82. 82. Information type
  83. 83. Subject
  84. 84. Language </li></ul>5. 4. 3. 2. 1. skos owl buy
  85. 85. Knowledge domains <ul><li>Geo
  86. 86. Organization
  87. 87. Information type
  88. 88. Subject
  89. 89. Language </li></ul>5. 4. 3. 2. 1. free skos owl buy
  90. 90. Ideas, rules of thumb <ul><li>Use OWL:Class for more tangible entities (e.g. organisations)
  91. 91. Use SKOS:ConceptScheme for more abstract entities (e.g. information type, subject)
  92. 92. Start modeling from RDF/XML and try keeping models so simple that connection and conversion to alternate models (e.g. Topic Maps) remains possible. </li></ul>
  93. 93. Work in progress <ul><li>Technical R&D issues: </li><ul><li>How to determine classes and conceptschemes?
  94. 94. How liberal or concise should our business rules be in order to achieve quality without discouraging contributors?
  95. 95. How to cope with change? e.g. Date in URI? See: http://www.jenitennison.com/blog/node/108 and http://www.jenitennison.com/blog/node/112 </li></ul><li>Management issues: </li><ul><li>many organisations and collections
  96. 96. time and money </li></ul></ul>
  97. 97. Dutch Government Metadata O verheid.nl W eb M etadata S tandaard: OWMS Hans Overbeek [email_address] DC2009

×