Updated Overview take 2.
authorbhyland
Tue, 07 May 2013 15:37:03 -0400
changeset 494 3c5488667adb
parent 493 1081ba4a2c4d
child 495 5e235f83bea8
Updated Overview take 2.
drafts/ld-glossary/Overview.html
--- a/drafts/ld-glossary/Overview.html	Tue May 07 15:24:58 2013 -0400
+++ b/drafts/ld-glossary/Overview.html	Tue May 07 15:37:03 2013 -0400
@@ -1,5 +1,5 @@
-<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.1//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd'>
-<html lang="en" dir="ltr">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 	<title>Linked Data Glossary</title>
 	<meta name="description" content="Linked Data Glossary">
@@ -144,7 +144,7 @@
     
     
       <dt>Latest editor's draft:</dt>
-      <dd><a href="http://dvcs.w3.org/hg/gld/gld-glossary/">http://dvcs.w3.org/hg/gld/gld-glossary/</a></dd>
+      <dd><a href="http://dvcs.w3.org/hg/gld/ld-glossary/">http://dvcs.w3.org/hg/gld/ld-glossary/</a></dd>
     
     
     
@@ -244,7 +244,7 @@
       
     
   
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#x5-star-linked-data"><span class="secno">1. </span>5 Star Linked Data</a></li><li class="tocline"><a class="tocxref" href="#apache-license"><span class="secno">2. </span>Apache License</a></li><li class="tocline"><a class="tocxref" href="#api"><span class="secno">3. </span>API</a></li><li class="tocline"><a class="tocxref" href="#authoritative-open-data"><span class="secno">4. </span>Authoritative Open Data</a></li><li class="tocline"><a class="tocxref" href="#creative-commons-licenses"><span class="secno">5. </span>Creative Commons Licenses</a></li><li class="tocline"><a class="tocxref" href="#cc-by-sa-license"><span class="secno">6. </span>CC-BY-SA License</a></li><li class="tocline"><a class="tocxref" href="#closed-world"><span class="secno">7. </span>Closed World</a></li><li class="tocline"><a class="tocxref" href="#connection"><span class="secno">8. </span>Connection</a></li><li class="tocline"><a class="tocxref" href="#conneg"><span class="secno">9. </span>Conneg</a></li><li class="tocline"><a class="tocxref" href="#content-negotiation"><span class="secno">10. </span>Content Negotiation</a></li><li class="tocline"><a class="tocxref" href="#controlled-vocabulary"><span class="secno">11. </span>Controlled Vocabulary</a></li><li class="tocline"><a class="tocxref" href="#converter"><span class="secno">12. </span>Converter</a></li><li class="tocline"><a class="tocxref" href="#csv"><span class="secno">13. </span>CSV</a></li><li class="tocline"><a class="tocxref" href="#curl"><span class="secno">14. </span>curl</a></li><li class="tocline"><a class="tocxref" href="#curies"><span class="secno">15. </span>CURIEs</a></li><li class="tocline"><a class="tocxref" href="#fragment-identifier"><span class="secno">16. </span>Fragment Identifier</a></li><li class="tocline"><a class="tocxref" href="#data-cloud"><span class="secno">17. </span>Data Cloud</a></li><li class="tocline"><a class="tocxref" href="#data-hub-the"><span class="secno">18. </span>Data Hub, The</a></li><li class="tocline"><a class="tocxref" href="#data-market"><span class="secno">19. </span>Data Market</a></li><li class="tocline"><a class="tocxref" href="#data-modeling"><span class="secno">20. </span>Data Modeling</a></li><li class="tocline"><a class="tocxref" href="#dataset"><span class="secno">21. </span>Dataset</a></li><li class="tocline"><a class="tocxref" href="#data-warehouse"><span class="secno">22. </span>Data Warehouse</a></li><li class="tocline"><a class="tocxref" href="#dbpedia"><span class="secno">23. </span>DBpedia</a></li><li class="tocline"><a class="tocxref" href="#dereferenceable-uris"><span class="secno">24. </span>Dereferenceable URIs</a></li><li class="tocline"><a class="tocxref" href="#description-logic"><span class="secno">25. </span>Description Logic</a></li><li class="tocline"><a class="tocxref" href="#dcat"><span class="secno">26. </span>DCAT</a></li><li class="tocline"><a class="tocxref" href="#dcmi"><span class="secno">27. </span>DCMI</a></li><li class="tocline"><a class="tocxref" href="#directed-graph"><span class="secno">28. </span>Directed Graph</a></li><li class="tocline"><a class="tocxref" href="#document-type-definition"><span class="secno">29. </span>Document Type Definition</a></li><li class="tocline"><a class="tocxref" href="#domain-name-system-dns"><span class="secno">30. </span>Domain Name System (DNS)</a></li><li class="tocline"><a class="tocxref" href="#dublin-core-metadata-element-set"><span class="secno">31. </span>Dublin Core Metadata Element Set</a></li><li class="tocline"><a class="tocxref" href="#dublin-core-metadata-initiative"><span class="secno">32. </span>Dublin Core Metadata Initiative</a></li><li class="tocline"><a class="tocxref" href="#entity"><span class="secno">33. </span>Entity</a></li><li class="tocline"><a class="tocxref" href="#etl"><span class="secno">34. </span>ETL</a></li><li class="tocline"><a class="tocxref" href="#free-libre-open-source-software"><span class="secno">35. </span>Free/Libre/Open Source Software</a></li><li class="tocline"><a class="tocxref" href="#government-open-data"><span class="secno">36. </span>Government Open Data</a></li><li class="tocline"><a class="tocxref" href="#graph"><span class="secno">37. </span>Graph</a></li><li class="tocline"><a class="tocxref" href="#hypertext-markup-language-html"><span class="secno">38. </span>HyperText Markup Language (HTML)</a></li><li class="tocline"><a class="tocxref" href="#hypertext-transfer-protocol"><span class="secno">39. </span>HyperText Transfer Protocol</a></li><li class="tocline"><a class="tocxref" href="#international-standards-organization-iso"><span class="secno">40. </span>International Standards Organization (ISO)</a></li><li class="tocline"><a class="tocxref" href="#internet-engineering-task-force-ietf"><span class="secno">41. </span>Internet Engineering Task Force (IETF)</a></li><li class="tocline"><a class="tocxref" href="#inference"><span class="secno">42. </span>Inference</a></li><li class="tocline"><a class="tocxref" href="#json"><span class="secno">43. </span>JSON</a></li><li class="tocline"><a class="tocxref" href="#json-ld"><span class="secno">44. </span>JSON-LD</a></li><li class="tocline"><a class="tocxref" href="#jena"><span class="secno">45. </span>Jena</a></li><li class="tocline"><a class="tocxref" href="#linked-data"><span class="secno">46. </span>Linked Data</a></li><li class="tocline"><a class="tocxref" href="#linked-data-client"><span class="secno">47. </span>Linked Data Client</a></li><li class="tocline"><a class="tocxref" href="#linked-data-platform-1.0"><span class="secno">48. </span>Linked Data Platform 1.0</a></li><li class="tocline"><a class="tocxref" href="#linked-data-principles"><span class="secno">49. </span>Linked Data Principles</a></li><li class="tocline"><a class="tocxref" href="#linked-open-data"><span class="secno">50. </span>Linked Open Data</a></li><li class="tocline"><a class="tocxref" href="#linked-open-data-cloud"><span class="secno">51. </span>Linked Open Data Cloud</a></li><li class="tocline"><a class="tocxref" href="#linked-open-data-cloud-diagram"><span class="secno">52. </span> Linked Open Data Cloud diagram</a></li><li class="tocline"><a class="tocxref" href="#linking-government-data"><span class="secno">53. </span>Linking Government Data</a></li><li class="tocline"><a class="tocxref" href="#linking-open-data-project"><span class="secno">54. </span>Linking Open Data Project</a></li><li class="tocline"><a class="tocxref" href="#linkset"><span class="secno">55. </span>Linkset</a></li><li class="tocline"><a class="tocxref" href="#machine-readable-data"><span class="secno">56. </span>Machine Readable Data</a></li><li class="tocline"><a class="tocxref" href="#message"><span class="secno">57. </span>Message</a></li><li class="tocline"><a class="tocxref" href="#metadata"><span class="secno">58. </span>Metadata</a></li><li class="tocline"><a class="tocxref" href="#metadata-object-description-schema"><span class="secno">59. </span>Metadata Object Description Schema</a></li><li class="tocline"><a class="tocxref" href="#modeling-process"><span class="secno">60. </span>Modeling Process</a></li><li class="tocline"><a class="tocxref" href="#n3"><span class="secno">61. </span>N3</a></li><li class="tocline"><a class="tocxref" href="#namespace"><span class="secno">62. </span>Namespace</a></li><li class="tocline"><a class="tocxref" href="#natural-keys"><span class="secno">63. </span>Natural Keys</a></li><li class="tocline"><a class="tocxref" href="#neutral-uri"><span class="secno">64. </span>Neutral URI</a></li><li class="tocline"><a class="tocxref" href="#object"><span class="secno">65. </span>Object</a></li><li class="tocline"><a class="tocxref" href="#ontology"><span class="secno">66. </span>Ontology</a></li><li class="tocline"><a class="tocxref" href="#ontology-matching"><span class="secno">67. </span>Ontology Matching</a></li><li class="tocline"><a class="tocxref" href="#open-government-data"><span class="secno">68. </span>Open Government Data</a></li><li class="tocline"><a class="tocxref" href="#open-world"><span class="secno">69. </span>Open World</a></li><li class="tocline"><a class="tocxref" href="#org-ontology"><span class="secno">70. </span>ORG Ontology</a></li><li class="tocline"><a class="tocxref" href="#persistent-identifier-scheme"><span class="secno">71. </span>Persistent Identifier Scheme</a></li><li class="tocline"><a class="tocxref" href="#persistent-uniform-resource-locator"><span class="secno">72. </span>Persistent Uniform Resource Locator</a></li><li class="tocline"><a class="tocxref" href="#predicate"><span class="secno">73. </span>Predicate</a></li><li class="tocline"><a class="tocxref" href="#provenance"><span class="secno">74. </span>Provenance</a></li><li class="tocline"><a class="tocxref" href="#protocol"><span class="secno">75. </span>Protocol</a></li><li class="tocline"><a class="tocxref" href="#public-sector-information"><span class="secno">76. </span>Public Sector Information</a></li><li class="tocline"><a class="tocxref" href="#purl"><span class="secno">77. </span>PURL</a></li><li class="tocline"><a class="tocxref" href="#quad-store"><span class="secno">78. </span>Quad Store</a></li><li class="tocline"><a class="tocxref" href="#query"><span class="secno">79. </span>Query</a></li><li class="tocline"><a class="tocxref" href="#r2rml"><span class="secno">80. </span>R2RML</a></li><li class="tocline"><a class="tocxref" href="#raw-data"><span class="secno">81. </span>Raw Data</a></li><li class="tocline"><a class="tocxref" href="#rdf"><span class="secno">82. </span>RDF</a></li><li class="tocline"><a class="tocxref" href="#rdfa"><span class="secno">83. </span>RDFa</a></li><li class="tocline"><a class="tocxref" href="#rdf-link"><span class="secno">84. </span>RDF link</a></li><li class="tocline"><a class="tocxref" href="#reasoner"><span class="secno">85. </span>Reasoner</a></li><li class="tocline"><a class="tocxref" href="#resource"><span class="secno">86. </span>Resource</a></li><li class="tocline"><a class="tocxref" href="#resource-description-framework"><span class="secno">87. </span>Resource Description Framework</a></li><li class="tocline"><a class="tocxref" href="#resource-description-framework-in-attributes"><span class="secno">88. </span>Resource Description Framework in Attributes</a></li><li class="tocline"><a class="tocxref" href="#rdf-database"><span class="secno">89. </span>RDF Database</a></li><li class="tocline"><a class="tocxref" href="#rdf-json"><span class="secno">90. </span>RDF-JSON</a></li><li class="tocline"><a class="tocxref" href="#rdf-schema"><span class="secno">91. </span>RDF Schema</a></li><li class="tocline"><a class="tocxref" href="#request"><span class="secno">92. </span>Request</a></li><li class="tocline"><a class="tocxref" href="#resource-1"><span class="secno">93. </span>Resource</a></li><li class="tocline"><a class="tocxref" href="#response"><span class="secno">94. </span>Response</a></li><li class="tocline"><a class="tocxref" href="#rest"><span class="secno">95. </span>REST</a></li><li class="tocline"><a class="tocxref" href="#rest-api"><span class="secno">96. </span>REST API</a></li><li class="tocline"><a class="tocxref" href="#schema"><span class="secno">97. </span>Schema</a></li><li class="tocline"><a class="tocxref" href="#semantic-technologies"><span class="secno">98. </span>Semantic Technologies</a></li><li class="tocline"><a class="tocxref" href="#semantic-web"><span class="secno">99. </span>Semantic Web</a></li><li class="tocline"><a class="tocxref" href="#semantic-web-stack"><span class="secno">100. </span>Semantic Web Stack </a></li><li class="tocline"><a class="tocxref" href="#semantic-web-standards"><span class="secno">101. </span>Semantic Web Standards</a></li><li class="tocline"><a class="tocxref" href="#semantic-web-search-engine"><span class="secno">102. </span>Semantic Web Search Engine</a></li><li class="tocline"><a class="tocxref" href="#service-oriented-architecture-soa"><span class="secno">103. </span>Service Oriented Architecture (SOA)</a></li><li class="tocline"><a class="tocxref" href="#sesame"><span class="secno">104. </span>Sesame</a></li><li class="tocline"><a class="tocxref" href="#skolemization"><span class="secno">105. </span>Skolemization</a></li><li class="tocline"><a class="tocxref" href="#simple-knowledge-organisation-system"><span class="secno">106. </span>Simple Knowledge Organisation System</a></li><li class="tocline"><a class="tocxref" href="#sparql"><span class="secno">107. </span>SPARQL</a></li><li class="tocline"><a class="tocxref" href="#sparql-client"><span class="secno">108. </span>SPARQL client</a></li><li class="tocline"><a class="tocxref" href="#sparql-endpoint"><span class="secno">109. </span>SPARQL endpoint</a></li><li class="tocline"><a class="tocxref" href="#structured-query-language-sql"><span class="secno">110. </span>Structured Query Language (SQL)</a></li><li class="tocline"><a class="tocxref" href="#subject"><span class="secno">111. </span>Subject</a></li><li class="tocline"><a class="tocxref" href="#taxonomy"><span class="secno">112. </span>Taxonomy</a></li><li class="tocline"><a class="tocxref" href="#term"><span class="secno">113. </span>Term</a></li><li class="tocline"><a class="tocxref" href="#triple"><span class="secno">114. </span>Triple</a></li><li class="tocline"><a class="tocxref" href="#triple-store"><span class="secno">115. </span>Triple store</a></li><li class="tocline"><a class="tocxref" href="#tuple"><span class="secno">116. </span>Tuple</a></li><li class="tocline"><a class="tocxref" href="#turtle"><span class="secno">117. </span>Turtle</a></li><li class="tocline"><a class="tocxref" href="#uniform-resource-identifier"><span class="secno">118. </span>Uniform Resource Identifier</a></li><li class="tocline"><a class="tocxref" href="#uniform-resource-locator"><span class="secno">119. </span>Uniform Resource Locator</a></li><li class="tocline"><a class="tocxref" href="#uri"><span class="secno">120. </span>URI</a></li><li class="tocline"><a class="tocxref" href="#url"><span class="secno">121. </span>URL</a></li><li class="tocline"><a class="tocxref" href="#validation-service"><span class="secno">122. </span>Validation Service</a></li><li class="tocline"><a class="tocxref" href="#vocabulary"><span class="secno">123. </span>Vocabulary</a></li><li class="tocline"><a class="tocxref" href="#void"><span class="secno">124. </span>VoID</a></li><li class="tocline"><a class="tocxref" href="#web-2.0"><span class="secno">125. </span>Web 2.0</a></li><li class="tocline"><a class="tocxref" href="#web-3.0"><span class="secno">126. </span>Web 3.0</a></li><li class="tocline"><a class="tocxref" href="#web-of-data"><span class="secno">127. </span>Web of Data</a></li><li class="tocline"><a class="tocxref" href="#web-ontology-language-owl"><span class="secno">128. </span>Web Ontology Language (OWL)</a></li><li class="tocline"><a class="tocxref" href="#world-wide-web-consortium-w3c"><span class="secno">129. </span>World Wide Web Consortium (<abbr title="World Wide Web Consortium">W3C</abbr>)</a></li><li class="tocline"><a class="tocxref" href="#extensible-hypertext-markup-language-xhtml"><span class="secno">130. </span>eXtensible Hypertext Markup Language (XHTML)</a></li><li class="tocline"><a class="tocxref" href="#extensible-markup-language-xml"><span class="secno">131. </span>eXtensible Markup Language (XML)</a></li><li class="tocline"><a class="tocxref" href="#xml-schema"><span class="secno">132. </span>XML Schema</a></li><li class="tocline"><a class="tocxref" href="#extensible-stylesheet-language-transformations-xslt"><span class="secno">133. </span>eXtensible Stylesheet Language Transformations (XSLT)</a></li><li class="tocline"><a class="tocxref" href="#acknowledgments"><span class="secno">A. </span>Acknowledgments</a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#x5-star-linked-data"><span class="secno">1. </span>5 Star Linked Data</a></li><li class="tocline"><a class="tocxref" href="#apache-license"><span class="secno">2. </span>Apache License</a></li><li class="tocline"><a class="tocxref" href="#api"><span class="secno">3. </span>API</a></li><li class="tocline"><a class="tocxref" href="#creative-commons-licenses"><span class="secno">4. </span>Creative Commons Licenses</a></li><li class="tocline"><a class="tocxref" href="#cc-by-sa-license"><span class="secno">5. </span>CC-BY-SA License</a></li><li class="tocline"><a class="tocxref" href="#closed-world"><span class="secno">6. </span>Closed World</a></li><li class="tocline"><a class="tocxref" href="#connection"><span class="secno">7. </span>Connection</a></li><li class="tocline"><a class="tocxref" href="#conneg"><span class="secno">8. </span>Conneg</a></li><li class="tocline"><a class="tocxref" href="#content-negotiation"><span class="secno">9. </span>Content Negotiation</a></li><li class="tocline"><a class="tocxref" href="#controlled-vocabulary"><span class="secno">10. </span>Controlled Vocabulary</a></li><li class="tocline"><a class="tocxref" href="#converter"><span class="secno">11. </span>Converter</a></li><li class="tocline"><a class="tocxref" href="#csv"><span class="secno">12. </span>CSV</a></li><li class="tocline"><a class="tocxref" href="#curl"><span class="secno">13. </span>curl</a></li><li class="tocline"><a class="tocxref" href="#curies"><span class="secno">14. </span>CURIEs</a></li><li class="tocline"><a class="tocxref" href="#fragment-identifier"><span class="secno">15. </span>Fragment Identifier</a></li><li class="tocline"><a class="tocxref" href="#data-cloud"><span class="secno">16. </span>Data Cloud</a></li><li class="tocline"><a class="tocxref" href="#data-hub-the"><span class="secno">17. </span>Data Hub, The</a></li><li class="tocline"><a class="tocxref" href="#data-market"><span class="secno">18. </span>Data Market</a></li><li class="tocline"><a class="tocxref" href="#data-modeling"><span class="secno">19. </span>Data Modeling</a></li><li class="tocline"><a class="tocxref" href="#dataset"><span class="secno">20. </span>Dataset</a></li><li class="tocline"><a class="tocxref" href="#data-warehouse"><span class="secno">21. </span>Data Warehouse</a></li><li class="tocline"><a class="tocxref" href="#dbpedia"><span class="secno">22. </span>DBpedia</a></li><li class="tocline"><a class="tocxref" href="#dereferenceable-uris"><span class="secno">23. </span>Dereferenceable URIs</a></li><li class="tocline"><a class="tocxref" href="#description-logic"><span class="secno">24. </span>Description Logic</a></li><li class="tocline"><a class="tocxref" href="#dcat"><span class="secno">25. </span>DCAT</a></li><li class="tocline"><a class="tocxref" href="#dcmi"><span class="secno">26. </span>DCMI</a></li><li class="tocline"><a class="tocxref" href="#directed-graph"><span class="secno">27. </span>Directed Graph</a></li><li class="tocline"><a class="tocxref" href="#document-type-definition"><span class="secno">28. </span>Document Type Definition</a></li><li class="tocline"><a class="tocxref" href="#domain-name-system-dns"><span class="secno">29. </span>Domain Name System (DNS)</a></li><li class="tocline"><a class="tocxref" href="#dublin-core-metadata-element-set"><span class="secno">30. </span>Dublin Core Metadata Element Set</a></li><li class="tocline"><a class="tocxref" href="#dublin-core-metadata-initiative"><span class="secno">31. </span>Dublin Core Metadata Initiative</a></li><li class="tocline"><a class="tocxref" href="#entity"><span class="secno">32. </span>Entity</a></li><li class="tocline"><a class="tocxref" href="#etl"><span class="secno">33. </span>ETL</a></li><li class="tocline"><a class="tocxref" href="#free-libre-open-source-software"><span class="secno">34. </span>Free/Libre/Open Source Software</a></li><li class="tocline"><a class="tocxref" href="#government-open-data"><span class="secno">35. </span>Government Open Data</a></li><li class="tocline"><a class="tocxref" href="#graph"><span class="secno">36. </span>Graph</a></li><li class="tocline"><a class="tocxref" href="#hypertext-markup-language-html"><span class="secno">37. </span>HyperText Markup Language (HTML)</a></li><li class="tocline"><a class="tocxref" href="#hypertext-transfer-protocol"><span class="secno">38. </span>HyperText Transfer Protocol</a></li><li class="tocline"><a class="tocxref" href="#http-uris"><span class="secno">39. </span>HTTP URIs</a></li><li class="tocline"><a class="tocxref" href="#international-standards-organization-iso"><span class="secno">40. </span>International Standards Organization (ISO)</a></li><li class="tocline"><a class="tocxref" href="#internet-engineering-task-force-ietf"><span class="secno">41. </span>Internet Engineering Task Force (IETF)</a></li><li class="tocline"><a class="tocxref" href="#inference"><span class="secno">42. </span>Inference</a></li><li class="tocline"><a class="tocxref" href="#json"><span class="secno">43. </span>JSON</a></li><li class="tocline"><a class="tocxref" href="#json-ld"><span class="secno">44. </span>JSON-LD</a></li><li class="tocline"><a class="tocxref" href="#jena"><span class="secno">45. </span>Jena</a></li><li class="tocline"><a class="tocxref" href="#linked-data"><span class="secno">46. </span>Linked Data</a></li><li class="tocline"><a class="tocxref" href="#linked-data-client"><span class="secno">47. </span>Linked Data Client</a></li><li class="tocline"><a class="tocxref" href="#linked-data-platform-1.0"><span class="secno">48. </span>Linked Data Platform 1.0</a></li><li class="tocline"><a class="tocxref" href="#linked-data-principles"><span class="secno">49. </span>Linked Data Principles</a></li><li class="tocline"><a class="tocxref" href="#linked-open-data"><span class="secno">50. </span>Linked Open Data</a></li><li class="tocline"><a class="tocxref" href="#linked-open-data-cloud"><span class="secno">51. </span>Linked Open Data Cloud</a></li><li class="tocline"><a class="tocxref" href="#linked-open-data-cloud-diagram"><span class="secno">52. </span> Linked Open Data Cloud diagram</a></li><li class="tocline"><a class="tocxref" href="#linking-government-data"><span class="secno">53. </span>Linking Government Data</a></li><li class="tocline"><a class="tocxref" href="#linking-open-data-project"><span class="secno">54. </span>Linking Open Data Project</a></li><li class="tocline"><a class="tocxref" href="#linkset"><span class="secno">55. </span>Linkset</a></li><li class="tocline"><a class="tocxref" href="#machine-readable-data"><span class="secno">56. </span>Machine Readable Data</a></li><li class="tocline"><a class="tocxref" href="#message"><span class="secno">57. </span>Message</a></li><li class="tocline"><a class="tocxref" href="#metadata"><span class="secno">58. </span>Metadata</a></li><li class="tocline"><a class="tocxref" href="#metadata-object-description-schema"><span class="secno">59. </span>Metadata Object Description Schema</a></li><li class="tocline"><a class="tocxref" href="#modeling-process"><span class="secno">60. </span>Modeling Process</a></li><li class="tocline"><a class="tocxref" href="#n3"><span class="secno">61. </span>N3</a></li><li class="tocline"><a class="tocxref" href="#namespace"><span class="secno">62. </span>Namespace</a></li><li class="tocline"><a class="tocxref" href="#natural-keys"><span class="secno">63. </span>Natural Keys</a></li><li class="tocline"><a class="tocxref" href="#neutral-uri"><span class="secno">64. </span>Neutral URI</a></li><li class="tocline"><a class="tocxref" href="#object"><span class="secno">65. </span>Object</a></li><li class="tocline"><a class="tocxref" href="#ontology"><span class="secno">66. </span>Ontology</a></li><li class="tocline"><a class="tocxref" href="#ontology-matching"><span class="secno">67. </span>Ontology Matching</a></li><li class="tocline"><a class="tocxref" href="#open-government-data"><span class="secno">68. </span>Open Government Data</a></li><li class="tocline"><a class="tocxref" href="#open-world"><span class="secno">69. </span>Open World</a></li><li class="tocline"><a class="tocxref" href="#org-ontology"><span class="secno">70. </span>ORG Ontology</a></li><li class="tocline"><a class="tocxref" href="#persistent-identifier-scheme"><span class="secno">71. </span>Persistent Identifier Scheme</a></li><li class="tocline"><a class="tocxref" href="#persistent-uniform-resource-locator"><span class="secno">72. </span>Persistent Uniform Resource Locator</a></li><li class="tocline"><a class="tocxref" href="#predicate"><span class="secno">73. </span>Predicate</a></li><li class="tocline"><a class="tocxref" href="#provenance"><span class="secno">74. </span>Provenance</a></li><li class="tocline"><a class="tocxref" href="#protocol"><span class="secno">75. </span>Protocol</a></li><li class="tocline"><a class="tocxref" href="#public-sector-information"><span class="secno">76. </span>Public Sector Information</a></li><li class="tocline"><a class="tocxref" href="#purl"><span class="secno">77. </span>PURL</a></li><li class="tocline"><a class="tocxref" href="#quad-store"><span class="secno">78. </span>Quad Store</a></li><li class="tocline"><a class="tocxref" href="#query"><span class="secno">79. </span>Query</a></li><li class="tocline"><a class="tocxref" href="#r2rml"><span class="secno">80. </span>R2RML</a></li><li class="tocline"><a class="tocxref" href="#raw-data"><span class="secno">81. </span>Raw Data</a></li><li class="tocline"><a class="tocxref" href="#rdf"><span class="secno">82. </span>RDF</a></li><li class="tocline"><a class="tocxref" href="#rdfa"><span class="secno">83. </span>RDFa</a></li><li class="tocline"><a class="tocxref" href="#rdf-link"><span class="secno">84. </span>RDF link</a></li><li class="tocline"><a class="tocxref" href="#reasoner"><span class="secno">85. </span>Reasoner</a></li><li class="tocline"><a class="tocxref" href="#resource"><span class="secno">86. </span>Resource</a></li><li class="tocline"><a class="tocxref" href="#resource-description-framework"><span class="secno">87. </span>Resource Description Framework</a></li><li class="tocline"><a class="tocxref" href="#resource-description-framework-in-attributes"><span class="secno">88. </span>Resource Description Framework in Attributes</a></li><li class="tocline"><a class="tocxref" href="#rdf-database"><span class="secno">89. </span>RDF Database</a></li><li class="tocline"><a class="tocxref" href="#rdf-json"><span class="secno">90. </span>RDF-JSON</a></li><li class="tocline"><a class="tocxref" href="#rdf-schema"><span class="secno">91. </span>RDF Schema</a></li><li class="tocline"><a class="tocxref" href="#request"><span class="secno">92. </span>Request</a></li><li class="tocline"><a class="tocxref" href="#resource-1"><span class="secno">93. </span>Resource</a></li><li class="tocline"><a class="tocxref" href="#response"><span class="secno">94. </span>Response</a></li><li class="tocline"><a class="tocxref" href="#rest"><span class="secno">95. </span>REST</a></li><li class="tocline"><a class="tocxref" href="#rest-api"><span class="secno">96. </span>REST API</a></li><li class="tocline"><a class="tocxref" href="#schema"><span class="secno">97. </span>Schema</a></li><li class="tocline"><a class="tocxref" href="#semantic-technologies"><span class="secno">98. </span>Semantic Technologies</a></li><li class="tocline"><a class="tocxref" href="#semantic-web"><span class="secno">99. </span>Semantic Web</a></li><li class="tocline"><a class="tocxref" href="#semantic-web-stack"><span class="secno">100. </span>Semantic Web Stack </a></li><li class="tocline"><a class="tocxref" href="#semantic-web-standards"><span class="secno">101. </span>Semantic Web Standards</a></li><li class="tocline"><a class="tocxref" href="#semantic-web-search-engine"><span class="secno">102. </span>Semantic Web Search Engine</a></li><li class="tocline"><a class="tocxref" href="#service-oriented-architecture-soa"><span class="secno">103. </span>Service Oriented Architecture (SOA)</a></li><li class="tocline"><a class="tocxref" href="#sesame"><span class="secno">104. </span>Sesame</a></li><li class="tocline"><a class="tocxref" href="#skolemization"><span class="secno">105. </span>Skolemization</a></li><li class="tocline"><a class="tocxref" href="#simple-knowledge-organisation-system"><span class="secno">106. </span>Simple Knowledge Organisation System</a></li><li class="tocline"><a class="tocxref" href="#sparql"><span class="secno">107. </span>SPARQL</a></li><li class="tocline"><a class="tocxref" href="#sparql-client"><span class="secno">108. </span>SPARQL client</a></li><li class="tocline"><a class="tocxref" href="#sparql-endpoint"><span class="secno">109. </span>SPARQL endpoint</a></li><li class="tocline"><a class="tocxref" href="#structured-query-language-sql"><span class="secno">110. </span>Structured Query Language (SQL)</a></li><li class="tocline"><a class="tocxref" href="#subject"><span class="secno">111. </span>Subject</a></li><li class="tocline"><a class="tocxref" href="#taxonomy"><span class="secno">112. </span>Taxonomy</a></li><li class="tocline"><a class="tocxref" href="#term"><span class="secno">113. </span>Term</a></li><li class="tocline"><a class="tocxref" href="#triple"><span class="secno">114. </span>Triple</a></li><li class="tocline"><a class="tocxref" href="#triple-store"><span class="secno">115. </span>Triple store</a></li><li class="tocline"><a class="tocxref" href="#tuple"><span class="secno">116. </span>Tuple</a></li><li class="tocline"><a class="tocxref" href="#turtle"><span class="secno">117. </span>Turtle</a></li><li class="tocline"><a class="tocxref" href="#uniform-resource-identifier"><span class="secno">118. </span>Uniform Resource Identifier</a></li><li class="tocline"><a class="tocxref" href="#uniform-resource-locator"><span class="secno">119. </span>Uniform Resource Locator</a></li><li class="tocline"><a class="tocxref" href="#uri"><span class="secno">120. </span>URI</a></li><li class="tocline"><a class="tocxref" href="#url"><span class="secno">121. </span>URL</a></li><li class="tocline"><a class="tocxref" href="#validation-service"><span class="secno">122. </span>Validation Service</a></li><li class="tocline"><a class="tocxref" href="#vocabulary"><span class="secno">123. </span>Vocabulary</a></li><li class="tocline"><a class="tocxref" href="#void"><span class="secno">124. </span>VoID</a></li><li class="tocline"><a class="tocxref" href="#web-2.0"><span class="secno">125. </span>Web 2.0</a></li><li class="tocline"><a class="tocxref" href="#web-3.0"><span class="secno">126. </span>Web 3.0</a></li><li class="tocline"><a class="tocxref" href="#web-of-data"><span class="secno">127. </span>Web of Data</a></li><li class="tocline"><a class="tocxref" href="#web-ontology-language-owl"><span class="secno">128. </span>Web Ontology Language (OWL)</a></li><li class="tocline"><a class="tocxref" href="#world-wide-web-consortium-w3c"><span class="secno">129. </span>World Wide Web Consortium (<abbr title="World Wide Web Consortium">W3C</abbr>)</a></li><li class="tocline"><a class="tocxref" href="#extensible-hypertext-markup-language-xhtml"><span class="secno">130. </span>eXtensible Hypertext Markup Language (XHTML)</a></li><li class="tocline"><a class="tocxref" href="#extensible-markup-language-xml"><span class="secno">131. </span>eXtensible Markup Language (XML)</a></li><li class="tocline"><a class="tocxref" href="#xml-schema"><span class="secno">132. </span>XML Schema</a></li><li class="tocline"><a class="tocxref" href="#extensible-stylesheet-language-transformations-xslt"><span class="secno">133. </span>eXtensible Stylesheet Language Transformations (XSLT)</a></li><li class="tocline"><a class="tocxref" href="#acknowledgments"><span class="secno">A. </span>Acknowledgments</a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></section>
 
 
 
@@ -286,189 +286,184 @@
 An Application Programming Interface (API) is an abstraction implemented in software that defines how others should make use of a software package such as a library or other reusable program.  APIs are used to provide developers access to data and functionality from a given system.
 </section>
 
-<section id="authoritative-open-data">
-<!--OddPage--><h2><span class="secno">4. </span>Authoritative Open Data</h2>
-Authoritative open data refers to open data that conforms to <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html" target="_blank">Best Practices for Publishing Linked Data</a> and which may be published by government and other responsible agencies.   Government agencies are often in a unique position and able to collect data that no other entity can. Open government data is nearly always collected at tax-payers expense and is viewed by the public and government, as valuable if made available with proper context and an open license. Linked Data is seen by many to be a useful approach to publish and consume authoritative open data.  An authoritative open data is often published by governments in linked data form and enjoys a greater chance of being discovered and re-used by others. See also [Government Open Data]. 
-</section>
-
 <section id="creative-commons-licenses">
-<!--OddPage--><h2><span class="secno">5. </span>Creative Commons Licenses</h2>
+<!--OddPage--><h2><span class="secno">4. </span>Creative Commons Licenses</h2>
 Creative Commons copyright licenses and tools aim to forge a balance inside the traditional “all rights reserved” setting that copyright law creates. Creative Commons licenses and tools provide a simple, standardized way to grant copyright permissions to their creative work. The combination of our tools and our users is a vast and growing digital commons, a pool of content that can be copied, distributed, edited, remixed, and built upon, all within the boundaries of copyright law. See also <a href="http://creativecommons.org/licenses/" target="_blank">About Creative Commons Licenses</a>.
 </section>
 
 <section id="cc-by-sa-license">
-<!--OddPage--><h2><span class="secno">6. </span>CC-BY-SA License</h2>
+<!--OddPage--><h2><span class="secno">5. </span>CC-BY-SA License</h2>
 CC-BY-SA is a form of Creative Commons license for resources released online. Work available under a <a href="http://creativecommons.org/licenses/by-sa/3.0/" target="_blank">CC-BY-SA license</a> means you can include it in any other work under the condition that you give proper attribution. If you create derivative works (such as modified or extended versions), then you must also license them as CC-BY-SA. 
 </section>
 
 <section id="closed-world">
-<!--OddPage--><h2><span class="secno">7. </span>Closed World</h2>
+<!--OddPage--><h2><span class="secno">6. </span>Closed World</h2>
 Closed world is a concept from Artificial Intelligence and refers to a model of uncertainty that an agent assumes about the external world. In a closed world, the agent presumes that what is not known to be true must be false. This is a common assumption underlying relational databases, most forms of logical programming. See also <a href="#open-world">Open World</a>.
 </section>
 
 <section id="connection">
-<!--OddPage--><h2><span class="secno">8. </span>Connection</h2>
+<!--OddPage--><h2><span class="secno">7. </span>Connection</h2>
 Connection is a concept from computer networking. It refers to a transport layer virtual circuit established between two programs for the purpose of communication. 
 </section>
 
 <section id="conneg">
-<!--OddPage--><h2><span class="secno">9. </span>Conneg</h2>
+<!--OddPage--><h2><span class="secno">8. </span>Conneg</h2>
 Abbreviated term for content negotiation. See also <a href="#content-negotiation">Content Negotiation</a>.
 </section>
 
 <section id="content-negotiation">
-<!--OddPage--><h2><span class="secno">10. </span>Content Negotiation</h2>
+<!--OddPage--><h2><span class="secno">9. </span>Content Negotiation</h2>
 Content negotiation, often called "conneg", refers to a phase in establishing a network connection. It is a mechanism for selecting the appropriate representation when servicing a request. The representation of entities in any response can be negotiated (including error responses). See also [<a href="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#content.negotiation" target="_blank">HTTP Protocol 1.1</a>]. See also <a href="#connection">Connection</a>. 
 </section>
 
 <section id="controlled-vocabulary">
-<!--OddPage--><h2><span class="secno">11. </span>Controlled Vocabulary</h2>
+<!--OddPage--><h2><span class="secno">10. </span>Controlled Vocabulary</h2>
 A controlled vocabulary is a selected set of terms that can be used to index, tag or describe units of information. By providing a restricted and managed set of terms they can be used to reduce ambiguity in information systems. Such vocabularies may be unstructured (e.g. code lists) or may be organized into increasingly complex knowledge organization schemes (<a href="#taxonomy">taxonomies</a>, thesauri, <a href="#ontology">ontologies</a>). In traditional settings the terms in the controlled vocabularies are words or phrases, in a linked data setting then they are normally assigned unique identifiers (URIs) which in turn link to descriptive phrases.
 </section>
 
 <section id="converter">
-<!--OddPage--><h2><span class="secno">12. </span>Converter</h2>
+<!--OddPage--><h2><span class="secno">11. </span>Converter</h2>
 Converter refers to a tool or script that converts data from one form to another, e.g., CSV into <a href="#rdf">RDF</a>. Publishing good quality, useful Linked Data requires expression of resources and how they are related. Linked Data modelers work with subject domain experts to make explicit the relationships between resources before converting a data set to RDF. 
 </section>
 
 <section id="csv">
-<!--OddPage--><h2><span class="secno">13. </span>CSV</h2>
+<!--OddPage--><h2><span class="secno">12. </span>CSV</h2>
 A CSV (comma separated value) file is a plain text file usually generated from a spreadsheet or database dump.  Each line or record contains fields separated by a comma.  CSV files may or may not contain column header names that may provide some information about the data.  From a Linked Data perspective, CSV files are considered 3-star data on the 5-star scale.
 </section>
 
 <section id="curl">
-<!--OddPage--><h2><span class="secno">14. </span>curl</h2>
+<!--OddPage--><h2><span class="secno">13. </span>curl</h2>
 Curl is a command line client to retrieve any data over a wide variety of protocols, including machine readable RDF. 
 </section>
 
 <section id="curies">
-<!--OddPage--><h2><span class="secno">15. </span>CURIEs</h2>
+<!--OddPage--><h2><span class="secno">14. </span>CURIEs</h2>
 CURIEs stands for "compact URI expressions" and is an RDFa approach for shortening URIs.
 </section>
 
 <section id="fragment-identifier">
-<!--OddPage--><h2><span class="secno">16. </span>Fragment Identifier</h2>
+<!--OddPage--><h2><span class="secno">15. </span>Fragment Identifier</h2>
 The part of an HTTP URI that follows a hash symbol (‘#’).  Fragment identifiers are not passed to Web servers by Web clients such as Web browsers.
 </section>
 
 
 <section id="data-cloud">
-<!--OddPage--><h2><span class="secno">17. </span>Data Cloud</h2>
+<!--OddPage--><h2><span class="secno">16. </span>Data Cloud</h2>
 Data cloud, also called the <a href="http://richard.cyganiak.de/2007/10/lod/" target="_blank">Linked Data Cloud</a>, is a visual representation of datasets published as Linked Data.  Using metadata generated by directories, including CKAN, the project records datasets by domain.  The Linked Data Cloud has doubled in size every 10 months since 2007 and as of late 2012 consists of more than 300 data sets from various domains, including geography, media, government and life sciences, according the [<a href="http://lod-cloud.net/state/" target="_blank">State of the LOD Cloud</a>], website and visualizations maintained by C. Bizer, A. Jentzsch, R. Cyganiak.  The original data owners/stewards publish one third of the data contained in the Linked Open Data Cloud, while third parties publish 67%.  Many academic institutions republish data from their respective governments as <a href="#linked-data">Linked Data</a>, often enhancing the representation in the process.
 </section>
 
 <section id="data-hub-the">
-<!--OddPage--><h2><span class="secno">18. </span>Data Hub, The</h2>
+<!--OddPage--><h2><span class="secno">17. </span>Data Hub, The</h2>
 <a href="http://thedatahub.org/" target="_blank">The Data Hub</a> is a specific site offering a community-run catalogue of data sets of data on the Internet, powered by the open-source data portal platform CKAN. <a href="http://thedatahub.org/" target="_blank">The Data Hub</a> is an openly editable open data catalogue in the style of Wikipedia.
 </section>
 
 <section id="data-market">
-<!--OddPage--><h2><span class="secno">19. </span>Data Market</h2>
+<!--OddPage--><h2><span class="secno">18. </span>Data Market</h2>
 A data market, also called a Data Marketplace, is an online (broker) service to enable discovery and access to a large collection of datasets offered by a range of data providers. Examples include Infochimps, Azure Marketplace and Factual.  Data Markets may include open as well as paid-for data, and may offer value added services such as <a href="#API">APIs</a> and visualizations and programmatic data access.
 </section>
 
 <section id="data-modeling">
-<!--OddPage--><h2><span class="secno">20. </span>Data Modeling</h2>
+<!--OddPage--><h2><span class="secno">19. </span>Data Modeling</h2>
 Data modeling is a process used to define and analyze data requirements for an information system.  In the context of Linked Data Modeling, it is a process that involves professional data modelers working closely with business stakeholders to define and document implicit and explicit  relationships.  Linked Data modeling applies formal Linked Data modeling techniques based on <a href="#linked-data-principles">Linked Data Principles</a>.
 </section>
 
 <section id="dataset">
-<!--OddPage--><h2><span class="secno">21. </span>Dataset</h2>
+<!--OddPage--><h2><span class="secno">20. </span>Dataset</h2>
 A collection of data, published or curated by a single agent, and available for access or download in one or more formats.
 </section>
 
 <section id="data-warehouse">
-<!--OddPage--><h2><span class="secno">22. </span>Data Warehouse</h2>
+<!--OddPage--><h2><span class="secno">21. </span>Data Warehouse</h2>
 A data warehouse is one approach to data integration in which data from various operational data systems is extracted, cleaned, transformed and copied to a centralized repository. The centralized repository can then be used for data mining or answering analytical queries.  By contrast, Linked Data <em>assumes and accounts</em> for a <em>distributed approach</em> using HTTP URIs to describe and access information resources.  A Linked Data approach is seen as an valid alternative to the centralized data warehouse approach especially when integrating open government datasets.
 </section>
 
 <section id="dbpedia">
-<!--OddPage--><h2><span class="secno">23. </span>DBpedia</h2>
+<!--OddPage--><h2><span class="secno">22. </span>DBpedia</h2>
 DBpedia is a community effort to extract structured information from Wikipedia and make it available on the Web. DBpedia is often depicted as a hub for the <a href="#data-cloud">Data Cloud</a>.  An RDF representation of the metadata derived from Wikipedia is made available for SPARQL queries and linking to other datasets on the Web.  DBpedia also provides a human readable version of the structured content.  For example, the human readable version of Linked Data for the color "Red" is found on DBpedia at <a href="http://dbpedia.org/page/Red" target="_blank">http://dbpedia.org/page/Red</a>.  See also [<a href="#curl">curl</a>].
 </section>
 
 <section id="dereferenceable-uris">
-<!--OddPage--><h2><span class="secno">24. </span>Dereferenceable URIs</h2>
+<!--OddPage--><h2><span class="secno">23. </span>Dereferenceable URIs</h2>
 When an HTTP client can look up a <a href="#uri">URI</a> using the HTTP protocol and retrieve a description of the resource, it is called a  dereferenceable URI.  Per Linked Data Principles, we identify things using HTTP URIs and provide information about them when an HTTP URI is resolved or dereferenced.  Dereferenceable URIs applies to URIs that are used to identify classic HTML documents and URIs that are used in the Linked Data context [<cite><a href="#bib-COOL-SWURIS" class="bibref">COOL-SWURIS</a></cite>] to identify real-world objects and abstract concepts.
 </section>
 
 <section id="description-logic">
-<!--OddPage--><h2><span class="secno">25. </span>Description Logic</h2>
+<!--OddPage--><h2><span class="secno">24. </span>Description Logic</h2>
 Description Logic (DL) is a family of knowledge representation languages with varying and adjustable expressivity.  DL is used in artificial intelligence for formal reasoning on the concepts of an application domain.  The Web Ontology Language (OWL) provides a standards-based way to exchange ontologies and includes a Description Logic semantics as well as an RDF based semantics.  Biomedical informatics applications often use DL for codification of healthcare and life sciences knowledge.
 </section>
 
 <section id="dcat">
-<!--OddPage--><h2><span class="secno">26. </span>DCAT</h2>
+<!--OddPage--><h2><span class="secno">25. </span>DCAT</h2>
 Data Catalog Vocabulary (DCAT) is an RDF vocabulary. It is designed to facilitate interoperability between data catalogs published on the Web. See also <a href="http://www.w3.org/TR/vocab-dcat/" target="_blank">Data Catalog Vocabulary (DCAT)</a>.
 </section>
 
 <section id="dcmi">
-<!--OddPage--><h2><span class="secno">27. </span>DCMI</h2>
+<!--OddPage--><h2><span class="secno">26. </span>DCMI</h2>
 See <a href="#dublin-core-metadata-initiative" target="_blank">Dublin Core Metadata Initiative</a>
 </section>
 
 <section id="directed-graph">
-<!--OddPage--><h2><span class="secno">28. </span>Directed Graph</h2>
+<!--OddPage--><h2><span class="secno">27. </span>Directed Graph</h2>
 A directed graph is a graph in which the links between nodes are directional, i.e., they only go from one node to another. RDF represents things (nouns) and the relationships between them (verbs) in a directed graph. In <a href="#rdf">RDF</a>, links are labelled by being assigned unique <a href="#uri">URIs</a>. 
 </section>
 
 <section id="document-type-definition">
-<!--OddPage--><h2><span class="secno">29. </span>Document Type Definition</h2>
+<!--OddPage--><h2><span class="secno">28. </span>Document Type Definition</h2>
 Document Type Definition (DTD) refers to a type of schema for defining a markup language, such as in XML or HTML (or their predecessor SGML). 
 </section>
 
 <section id="domain-name-system-dns">
-<!--OddPage--><h2><span class="secno">30. </span>Domain Name System (DNS)</h2> 
+<!--OddPage--><h2><span class="secno">29. </span>Domain Name System (DNS)</h2> 
 Domain Name System (DNS) refers to the Internet's mechanism for mapping between a human-readable host name (e.g. <a href="http://www.example.com" target="_blank">www.example.com</a>) and an Internet Protocol (IP) Address (e.g. 203.20.51.10).
 </section>
 
 <section id="dublin-core-metadata-element-set">
-<!--OddPage--><h2><span class="secno">31. </span>Dublin Core Metadata Element Set</h2>
+<!--OddPage--><h2><span class="secno">30. </span>Dublin Core Metadata Element Set</h2>
 Dublin Core Metadata Element Set refers to a <a href="#vocabulary">vocabulary</a> of fifteen properties for use in resource descriptions, such as may be found in a library card catalog (creator, publisher, etc).  The Dublin Core Metadata Element Set, also known as "DC Elements", is the most commonly used vocabulary for Linked Data applications. See also <a href="http://dublincore.org/documents/dces/" target="_blank"> Dublin Core Element Set, Version 1.1 Specification.</a> [<a href="#dublin-core-metadata-initiative" target="_blank">DCMI</a>]
 </section>
 
 <section id="dublin-core-metadata-initiative">
-<!--OddPage--><h2><span class="secno">32. </span>Dublin Core Metadata Initiative</h2> 
+<!--OddPage--><h2><span class="secno">31. </span>Dublin Core Metadata Initiative</h2> 
 <a href="http://dublincore.org/about-us/" target="_blank">The Dublin Core Metadata Initiative (DCMI)</a> is an open international organization engaged in the development of interoperable metadata standards, including the Dublin Core Element Set. The DCMI manages long term curation and development of DCMI <a href="http://dublincore.org/specifications/" target="_blank"> specifications and metadata terms namespaces</a>
 </section>
 
 <section id="entity">
-<!--OddPage--><h2><span class="secno">33. </span>Entity</h2>
+<!--OddPage--><h2><span class="secno">32. </span>Entity</h2>
 The term entity refers to anything that can be named using an HTTP URL. It serves as the <a href="#subject">Subject</a> of a description. 
 </section>
 
 <section id="etl">
-<!--OddPage--><h2><span class="secno">34. </span>ETL</h2>
+<!--OddPage--><h2><span class="secno">33. </span>ETL</h2>
 ETL is an abbreviation for extact, transform, load.  Linked Data modelers and developers extract data from a relational database, transform to a Linked Data serialization, and then load it into an RDF database.
 </section>
 
 <section id="free-libre-open-source-software">
-<!--OddPage--><h2><span class="secno">35. </span>Free/Libre/Open Source Software</h2>
+<!--OddPage--><h2><span class="secno">34. </span>Free/Libre/Open Source Software</h2>
 Free, also known as Libre or Open Source, is a generic and internationalized term for software released under an Open Source license.
 </section>
 
 <section id="government-open-data">
-<!--OddPage--><h2><span class="secno">36. </span>Government Open Data</h2>
+<!--OddPage--><h2><span class="secno">35. </span>Government Open Data</h2>
 Many government authorities have mandated publication of data to the public Web. The broad intention is to facilitate the maintenance of open societies and support governmental accountability and transparency initiatives. However, publication of unstructured data on the World Wide Web is in itself insufficient; in order to realize the goals of efficiency, transparency and accountability, re-use of published data means members of the public must be able to absorb data in ways that can be readily found and absorbed programmatically by machines, and visualized by humans.  <a href="#linked-data-principals">Linked Data Principles</a> address many of the data modeling and format requirements to realize the goals of Open Government Data. 
 </section>
 
 <section id="graph">
-<!--OddPage--><h2><span class="secno">37. </span>Graph</h2>
+<!--OddPage--><h2><span class="secno">36. </span>Graph</h2>
 Graph refers to a mathematical structure consisting of a collection of objects, represented by "nodes", and connected by “edges” (also called links), to denote inter-relationships between them. It is well established as the field of Graph Theory.  See also <a href="#directed-graph">Directed Graph</a>.
 </section>
 
 <section id="hypertext-markup-language-html">
-<!--OddPage--><h2><span class="secno">38. </span>HyperText Markup Language (HTML)</h2> 
+<!--OddPage--><h2><span class="secno">37. </span>HyperText Markup Language (HTML)</h2> 
 HyperText Markup Language (HTML) is the predominant markup language for hypertext pages on the Web. HTML defines the structure of Web pages and it is a family of <abbr title="World Wide Web Consortium">W3C</abbr> standards.
 </section>
 
 <section id="hypertext-transfer-protocol">
-<!--OddPage--><h2><span class="secno">39. </span>HyperText Transfer Protocol</h2> 
+<!--OddPage--><h2><span class="secno">38. </span>HyperText Transfer Protocol</h2> 
 HyperText Transfer Protocol (HTTP) is the standard transmission protocol [<cite><a href="#bib-RFC2616" class="bibref">RFC2616</a></cite>] used on the World Wide Web to transfer hypertext requests and information between Web servers and Web clients (such as browsers). It is an IETF standard.  
 </section>
 
-<section>
-HTTP URIs
+<section id="http-uris">
+<!--OddPage--><h2><span class="secno">39. </span>HTTP URIs</h2>
 See <a href="uniform-resource-identifier">Uniform Resource Identifier (URI)</a>.
 </section>
 
@@ -499,7 +494,7 @@
 
 <section id="jena">
 <!--OddPage--><h2><span class="secno">45. </span>Jena</h2>
-<a ="http:="" jena.apache.org"="">Jena</a> is an Open Source Software implementation of a <a href="#semantic-web">Semantic Web</a> development framework. It supports the storage, retrieval and analysis of <a href="#rdf">RDF</a> information. 
+<a href="http://jena.apache.org">Jena</a> is an Open Source Software implementation of a <a href="#semantic-web">Semantic Web</a> development framework. It supports the storage, retrieval and analysis of <a href="#rdf">RDF</a> information. 
 </section>
 
 <section id="linked-data">
@@ -559,14 +554,16 @@
 </section>
 
 <section id="machine-readable-data">
-<!--OddPage--><h2><span class="secno">56. </span>Machine Readable Data</h2> 
-Machine readable data refers to data which can be seamlessly processed by programs. It often means non-graphics data which gets 2-stars on the  <a href="#5-star-linked-data">5-star Linked Data scale</a>. While some open data developers use screen-scrapping techniques to parse machine readable content, using 4-star or 5-star Linked Data is preferable in terms of provenance and ease of reuse. Anything less than 4-star data gives Web developers more work modeling and transforming data. By creating and publishing Linked Data, you are increasing the ability of search engines, and thus humans, to find, access and re-use information.  
-<p></p>
+<!--OddPage--><h2><span class="secno">56. </span>Machine Readable Data</h2>
+<p>Machine readable data refers to data that can be processed by programs.  By creating and publishing Linked Data, you are increasing the ability of search engines, and thus humans to find, access and re-use information.  Once found, programs can re-use data without custom coding.  
+</p>
 <p>
-To see how a Linked Data representation yields both a human and machine readable version simultaneously, try this exercise. Wikipedia has an interesting page about the color <a href="http://wikipedia.org/wiki/Red" target="_blank">Red</a>.  DBpedia allows you to get the structured content listed on the Wikipedia page for "Red" [<a href="http://wikipedia.org/wiki/Red" target="_blank">http://wikipedia.org/wiki/Red</a>] by changing "wiki" to "data" and appending the appropriate file extension.  
-</p><pre>$ curl -L http://dbpedia.org/data/Red.ttl</pre>
+To see how a Linked Data representation yields both a human and machine readable version simultaneously, try this exercise. Wikipedia has an interesting page about the color <a href="http://wikipedia.org/wiki/Red" target="_blank">Red</a>.  DBpedia allows you to get the structured content listed on the Wikipedia page for "Red" [<a href="http://wikipedia.org/wiki/Red" target="_blank">http://wikipedia.org/wiki/Red</a>] by changing "wiki" to "data" and appending the appropriate file extension.
+</p>
+<pre>$ curl -L http://dbpedia.org/data/Red.ttl</pre> 
+<p>
 Thus, you've seen how the same data can be viewed in human and machine readable format from the same page.
-<p></p>
+</p>
 </section>
 
 <section id="message">
@@ -723,8 +720,8 @@
 
 <section id="resource-description-framework">
 <!--OddPage--><h2><span class="secno">87. </span>Resource Description Framework</h2>
-Resource Description Framework (RDF), is a general-purpose language for representing information in the Web.  RDF provides a common model for Linked Data and is well suited for the representation of data on the Web.  RDF is <b>not</b> a data format, rather a model for expressing relationships between arbitrary data elements that may be represented in a variety of standard formats.  RDF is based on the idea of identifying things using Web identifiers or <a href="#uris">HTTP URIs</a>, and describing resources in terms of simple properties and property values. A single RDF statement describes two things and a relationship between them. This enables RDF to represent simple statements about resources as a graph of nodes and arcs representing the resources, and their properties and values.  Linked Data developers call the three elements in an RDF statement the <em>subject</em>, the <em>predicate</em> and the <em>object</em>. See also [<h ref="http://www.w3.org/TR/rdf11-concepts/">RDF 1.1 Concepts and Abstract Syntax
-</h></section>
+Resource Description Framework (RDF), is a general-purpose language for representing information in the Web.  RDF provides a common model for Linked Data and is well suited for the representation of data on the Web.  RDF is <b>not</b> a data format, rather a model for expressing relationships between arbitrary data elements that may be represented in a variety of standard formats.  RDF is based on the idea of identifying things using Web identifiers or <a href="#uris">HTTP URIs</a>, and describing resources in terms of simple properties and property values. A single RDF statement describes two things and a relationship between them. This enables RDF to represent simple statements about resources as a graph of nodes and arcs representing the resources, and their properties and values.  Linked Data developers call the three elements in an RDF statement the <em>subject</em>, the <em>predicate</em> and the <em>object</em>. See also [<a href="http://www.w3.org/TR/rdf11-concepts/">RDF 1.1 Concepts and Abstract Syntax</a>
+</section>
 
 <section id="resource-description-framework-in-attributes">
 <!--OddPage--><h2><span class="secno">88. </span>Resource Description Framework in Attributes</h2>
@@ -754,12 +751,12 @@
 
 <section id="resource-1">
 <!--OddPage--><h2><span class="secno">93. </span>Resource</h2>
-A resource is a network data object or service that can be identified by an HTTP URI. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or vary in other ways. See details from RFC 2616bis for details on Uniform Resource Identifiers. See details from RFC 2616bis for details on <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#uri.303" target="blank">Uniform Resource Identifiers</a>.
+A resource is a network data object or service that can be identified by an HTTP URI. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or vary in other ways. See details from RFC 2616bis for details on Uniform Resource Identifiers. See details from RFC 2616bis for details on <a href="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#uri.303" target="blank">Uniform Resource Identifiers</a>.
 </section>
 
 <section id="response">
 <!--OddPage--><h2><span class="secno">94. </span>Response</h2>
-Response refers to a stage in the HTTP protocol. After receiving and interpreting a request message, a server responds with an HTTP response message.   See also [<cite><a href="#bib-RFC2616" class="bibref">RFC2616</a></cite>] bis for an <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#response" target="blank">HTTP Response</a> message.
+Response refers to a stage in the HTTP protocol. After receiving and interpreting a request message, a server responds with an HTTP response message.   See also [<cite><a href="#bib-RFC2616" class="bibref">RFC2616</a></cite>] bis for an <a href="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#response" target="blank">HTTP Response</a> message.
 </section>
 
 <section id="rest">
@@ -881,9 +878,9 @@
 <!--OddPage--><h2><span class="secno">118. </span>Uniform Resource Identifier</h2>
 <p>A Uniform Resource Identifier (URI) is a global identifier that uniquely identifies an abstract or physical resource.  URIs were standardized by joint action of the <abbr title="World Wide Web Consortium">W3C</abbr> and IETF.  URI’s provide a simple and extensible means for identifying a resource.  URIs play a key role in enabling Linked Data. URIs can be used to uniquely identify virtually anything including a physical building or more abstract concepts like the color red. If you would like to see the URI for the color red for example, the DBpedia project has modified URLs from the Wikipedia entry to create <a href="http://dbpedia.org/page/red" target="_blank">http://dbpedia.org/page/red</a>.  URIs can also be used to refer to other data representations such as a row in a CSV file or a specific table in a relational database. 
 </p>
-<p></p>
+<p>
 As Linked Data builds directly on Web architecture, the term "resource" is used to refer to things of interest that are identified by HTTP URIs.  An HTTP URI may or may not be resolvable on the Web.  URIs have been known by many names: Web addresses, Universal Document Identifiers, Universal Resource Identifiers, and finally the combination of Uniform Resource Identifier.  If you are interested in the history of the many names, read Tim Berners-Lee's design document <a href="http://www.w3.org/DesignIssues/Architecture.html" target="_blank">Web Architecture from 50,000 feet</a>. For definitive information on Uniform Resource Identifiers (URI), see "Uniform Resource Identifier (URI): Generic Syntax," [<cite><a href="#bib-RFC3986" class="bibref">RFC3986</a></cite>]
-<p></p>
+</p>
 </section>
 
 <section id="uniform-resource-locator">
@@ -993,4 +990,4 @@
 </dd><dt id="bib-LDP-ONE">[LDP-ONE]</dt><dd><cite><a href="http://www.w3.org/TR/2013/WD-ldp-20130307/">Linked Data Platform 1.0.</a></cite> Steve Speicher, John Arwe. 07 March 2013. W3C Working Draft, Linked Data Platform Working Group. URL: <a href="http://www.w3.org/TR/ldp/">http://www.w3.org/TR/ldp/</a>
 </dd><dt id="bib-LINKED-DATA">[LINKED-DATA]</dt><dd><cite><a href="http://www.w3.org/DesignIssues/LinkedData.html">LINKED-DATA</a></cite>, Tim Berners-Lee. Linked Data Design Issues. 27 July 2006. W3C-Internal Document. URL: <a href="http://www.w3.org/DesignIssues/LinkedData.html">http://www.w3.org/DesignIssues/LinkedData.html</a>
 </dd><dt id="bib-N3">[N3]</dt><dd><cite><a href="http://www.w3.org/TeamSubmission/n3/">Notation3 (N3): A readable RDF syntax</a></cite>, Tim Berners-Lee, Dan Connolly,  28 March 2011. W3C Team Submission. URL: <a href="http://www.w3.org/TeamSubmission/n3/">http://www.w3.org/TeamSubmission/n3/</a>
-</dd></dl></section></section></body></html>
+</dd></dl></section></section></body></html>
\ No newline at end of file