Update glossary with additional terms
authorbhyland
Mon, 26 Mar 2012 11:11:03 -0400
changeset 133 21be7f43d7d6
parent 132 8ccd1b1144c7
child 134 b51ca1a629a6
Update glossary with additional terms
bp/index.html
bp/respec-config.js
glossary/index.html
glossary/respec-config.js
--- a/bp/index.html	Thu Mar 22 15:05:31 2012 +0000
+++ b/bp/index.html	Mon Mar 26 11:11:03 2012 -0400
@@ -25,6 +25,32 @@
   <p>This document is work in progress. The GLD WG ongoing discussions are recorded on the <a href="http://www.w3.org/2011/gld/wiki/Best_Practices_Discussion_Summary">Best Practices Wiki page</a></p>
 </section>
 
+<!-- Structure of Best 
+
+<!-- List of Best Practices -->
+
+The following best practices are discussed in this document and listed here for convenience.
+
+Select data sets that other people may wish to re-use.
+
+Re-use vocabularies whenever possible
+
+Identify relevant words that describe the main ideas or concepts
+
+Search for vocabularies using semantic search sites and dataset catalogues
+
+Ensure new vocabularies you create pass the "Vocabulary Creation Criteria Checklist"
+* Vocabulary is self-descriptive
+* Vocabulary is described in more than one language, ideally
+* Vocabulary will be accessible for a long period (has longevity)
+
+Ensure vocabularies you choose pass the "Vocabulary Selection Criteria Checklist"
+* Ensure vocabularies you use are published by a trusted group or organization
+* Ensure vocabularies have permanent URI
+* Confirm the versioning policy 
+
+
+
 
 <!--    INTRODUCTION    -->
 
@@ -51,29 +77,21 @@
 Linked Data uses a family of international standards and best practices for the publication, dissemination and reuse of structured data. Linked Data, unlike previous data formatting and publication approaches, provides a simple mechanism for combining data from multiple sources across the Web. 
 </p>
 
-<h2>Government Motivation for Publishing Linked Open Data</h2>
+<h2>Government Motivation to Publish Linked Open Data</h2>
 <p>
-Many governments have mandated publication of open government data to the public Web. The intention of these mandates are 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 via search, visualized and absorbed programmatically.
+Governments worldwide have mandated publication of open government data to the public Web. The intention of these mandates 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 via search, visualized and absorbed programmatically.
 </p>
 
+The best practices provided provide a methodical approach for the creation, publication and dissemination of government Linked Data. Guidance on the life cycle of a Linked Data project, beginning with identification of suitable data sets, modeling, vocabulary selection, through publication and ongoing maintenance are provided.  Since publishing data to the Web following Linked Data principles is considering an emerging publication mode for governments, guidance for procurement of necessary services is provided to help inform government stakeholders.
 </section>
 
 
-<section>
-<h3>Motivation</h3>
-The best practices provided here are provide a methodical approach for the creation, publication and dissemination of government Linked Data, including:
-<ul>
-	<li> Description of the life cycle of a Linked Data project, starting with identification of suitable data sets, modeling, vocabulary selection, through publication and ongoing maintenance.</li>
-	<li> Definition of proven steps to create and maintain government data sets using Linked Data principles.</li>
-	<li> Guidance in the procurement process for publishing Linked Open Data.
-</ul>
 
+<h3> Linked Open Data Lifecycle </h3>
 <p class='issue'>Does it make sense to base the GLD life cycle on one of the general LD life cycles? See <a href="https://www.w3.org/2011/gld/track/issues/15">ISSUE-15</a></p>
 </section>
 
 <section>
-<p>Currently we have identified the following Government Linked Data Life Cycles
-</p>
 <p class="todo"> Include a brief description for each one of them.
 </p>
 <p>Hyland et al.</p>
@@ -84,8 +102,9 @@
 <img src="img/GLF_Hausenblas.PNG" width="600"/>
 <p>Villazon-terrazas</p>
 <img src="img/GLF_Villazon-terrazas.PNG" width="600" />
+</section>
 
-</section>
+
 <!--    PROCUREMENT   -->
 <section>
 <h3>Procurement</h3>
@@ -95,12 +114,22 @@
 </p>
 
 <p>
-Linked Open Data (LOD) offers novel approaches for publishing and consuming data on the Web. This procurement overview and companion glossary is intended to help contract officers and their technical representatives understand LOD activities, and their associated products and services. It is hoped that this will aid government officials in procuring LOD related products and services.
+Linked Open Data (LOD) offers novel approaches for publishing and consuming data on the Web. This procurement overview and companion glossary is intended to help contract officers and their technical representatives understand LOD activities, and their associated products and services. This guidance is intended to aid government officials in the procurement process.
 </p>
 
 <h4>Overview</h4>
 <p>
-LOD provisions data into the Web so it can be interlinked with other linked data, making it easier to discover, and more useful and reusable. LOD leverages World Wide Web standards such as Hypertext Transfer Protocol (HTTP), Resource Description Framework (RDF), and Uniform Resource Identifiers (URIs), which make data self-describing so that it is both human and machine readable. Self-describing data is important because most government data comes from relational data systems that do not fully describe the source data schema needed for application development by third parties.
+LOD provisions data into the Web so it can be interlinked with other linked data, making it easier to discover, and more useful and reusable. Linked Open Data is based on W3C including Hypertext Transfer Protocol (HTTP), Uniform Resource Identifiers (URIs), and Resource Description Framework (RDF) family of standards.  
+</p>
+
+</p>
+Publish structured content as <em>self-describing</em> Linked Data.
+
+Currently, the majority of structured data collected and curated by governments worldwide resides in relational data systems.  A logical schema for this structured content is typically maintained external to the data itself.  
+
+Understanding the schema, among other characteristics of the data, is necessary for data re-use.  Regardless of whether data is being re-used internally or externally to the original data owner, the <em>schema</em> or structure and organization of the data must be understood by those analyzing the data itself.
+
+Data published in an RDF format <em>combines the schema with the data</em> itself, which is what makes it self-describing.
 </p>
 
 <h5>LOD Production through Consumption Lifecycle</h5>
@@ -358,7 +387,7 @@
 
 <!-- << URI CONSTRUCTION   -->
 <section>
-<h3>URI Construction - Boris</h3>
+<h3>URI Construction</h3>
 <p class='responsible'>Ghislain Atemezing (INSTITUT TELECOM), Michael Hausenblas (DERI), Boris Villazon-Terrazas (UPM), Daniel Vila (UPM), John Erickson (RPI), Martin Alvarez (CTIC)</p>
 <p>
 This section specifies how to create good URIs for use in government linked data. Inputs include 
--- a/bp/respec-config.js	Thu Mar 22 15:05:31 2012 +0000
+++ b/bp/respec-config.js	Mon Mar 26 11:11:03 2012 -0400
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "ED",
-    publishDate:          "2012-02-23",
+    publishDate:          "2012-03-22",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/
--- a/glossary/index.html	Thu Mar 22 15:05:31 2012 +0000
+++ b/glossary/index.html	Mon Mar 26 11:11:03 2012 -0400
@@ -16,13 +16,13 @@
 
 <section id="abstract">
 
-<p> This document is a glossary of terms defined and used in the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html">Best Practice Document </a>Working Note. It is intended for use by Government Linked Data publishers and consumers in order to refer to a common coherent set of terminologies. 
+<p> This document is a glossary of terms defined and used in the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html">Linked Data Best Practices Recommendation</a> published by the W3C Government Linked Data Working Group. It is intended for use by Linked Data publishers and consumers in order to refer to a common glossary of terms. 
 </p>
-<p class="todo">@@TODO EXPAND MORE @@</p>
 </section>
 
 <section id="sotd">
-
+  <p>This document is work in progress.  It will be reviewed in 2012 and published along with the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html"> Best Practices for Publishing Linked Data</a> document.
+  </p>
 </section>
 
 <section class="introductory">
@@ -36,11 +36,10 @@
 </section>
 
 
-
-<section id="abox">
-<h4> Abox </h4>
-One of two types of statements in an <a href="#ontology">ontology</a> (the other being <a href="#tbox">Tbox</a>).  Abox statements represent facts (or "assertions", hence the "A"), e.g. John is a Person (where Person is a defined class).
-</section>
+   // <section id="abox">
+   // <h4> Abox </h4>
+   //One of two types of statements in an <a href="#ontology">ontology</a> (the other being <a href="#tbox">Tbox</a>).  Abox statements represent facts (or "assertions", hence the "A"), e.g. John is a Person (where Person is a defined class).
+   // </section>
 
 <section id="api">
 <h4>Application Programmer Interface(API)</h4>
@@ -64,6 +63,16 @@
 </section>
 
 <section >
+<h4>Connection</h4>
+A transport layer virtual circuit established between two programs for the purpose of communication.
+</section>
+
+<section>
+<h4>Content Negotiation</h4>
+The mechanism for selecting the appropriate representation when servicing a request. The representation of entities in any response can be negotiated (including error responses).  See details from RFC 2616bis for an <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#content.negotiation"> target="blank">Content Negotation</a>.
+</section>
+
+<section >
 <h4>Controlled Vocabularies</h4>
 Carefully selected sets of terms that are used to describe units of information; used to create thesauri,  taxonomies and ontologies.
 </section>
@@ -93,7 +102,6 @@
 <p class="todo">@@TODO: [email protected]@</p>
 </section >
 
-
 <section >
 <h4>DBpedia</h4>
 An RDF representation of the metadata held in Wikipedia and made available for SPARQL query on the World Wide Web.
@@ -209,6 +217,12 @@
 </section>
 
 <section>
+<h4>Message</h4> 
+The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined as an <a href="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#httpmessage" target="blank">HTTP Message</a> and transmitted via the connection.
+</section>
+
+
+<section>
 <h4>Metadata</h4> 
 Information used to administer, describe, preserve, present, use or link other information held in resources, especially knowledge resources, be they physical or virtual.
 </section>
@@ -287,9 +301,22 @@
 
 <section>
 <h4>RDFS</h4>
-RDFS is the schema language for RDF; it describes constructs for types of objects (Classes), relating 
-types to one another (subClasses), properties that describe objects (Properties), and relationships
-between them (subProperty).
+RDFS is the schema language for RDF; it describes constructs for types of objects (Classes), relating types to one another (subClasses), properties that describe objects (Properties), and relationships between them (subProperty).
+</section>
+
+<section>
+<h4>Request</h4>
+A request message from a client to a server includes, within the first line of that message, the method to be applied to the resource, the identifier of the resource, and the protocol version in use.  See details from RFC 2616bis for a <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#request"> target="blank">HTTP Request</a>.
+</section>
+
+<section>
+<h4>Resource</h4>
+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 <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#uri.303"> target="blank">Uniform Resource Identifiers</a>.
+</section>
+
+<section>
+<h4>Response</h4>
+After receiving and interpreting a request message, a server responds with an HTTP response message.  See details from RFC 2616bis 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.
 </section>
 
 <section>
@@ -327,11 +354,6 @@
 </section>
 
 <section>
-<h4>Silk</h4>
-Silk(Silk Link Discovery Framework) is a tool for discovering relationships between data items within different Linked Data sources.
-</section>
-
-<section>
 <h4>Simple Knowledge Organisation System</h4> 
 A vocabulary description language for RDF designed for representing traditional knowledge organization systems such as enterprise taxonomies in RDF. A W3C standard.
 </section>
@@ -398,7 +420,9 @@
 
 <section >
 <h4>Uniform Resource Identifiers (URIs)</h4>
- URI’s play a key role in enabling linked data. To publish data on the Web, the items in a domain of interest must first be identified. These are the things whose properties and relationships will be described in the data, and may include Web documents as well as real-world entities and abstract concepts. As Linked Data builds directly on Web architecture [[!WEBARCH]], the Web architecture term resource is used to refer to these things of interest, which are, in turn, identified by HTTP URIs. 
+URI’s play a key role in enabling Linked Data. To publish data on the Web, the items in a domain of interest must first be identified. These are the things whose properties and relationships will be described in the data, and may include Web documents as well as real-world entities and abstract concepts. As Linked Data builds directly on Web architecture, the Web architecture term "resource" is used to refer to these things of interest, which are, in turn, identified by HTTP URIs. 
+
+URIs have been known by many names: Web addresses, Universal Document Identifiers, Universal Resource Identifiers [RFC1630], and finally the combination of Uniform Resource Indetifiers.  As far as HTTP is concerned, Uniform Resource Identifiers (URI's) are simply formatted strings which identify via name, location, or any other characteristic, a resource.  For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers (URI): Generic Syntax and Semantics," [RFC2396] 
 </section >
 
 <section >
@@ -454,8 +478,15 @@
 </section>
 
 
+<!-- References -->
+<section class="references">
+<p>
+
+[RFC1630] 	Berners-Lee, T., <a href="http://tools.ietf.org/html/rfc1630">“Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web”<a>, RFC 1630, June 1994.
+[RFC2396]	Berners-Lee, T., Fielding, R.T., and L. Masinter, <a ref="http://tools.ietf.org/html/rfc2396">“Uniform Resource Identifiers (URI): Generic Syntax”</a>, RFC 2396, August 1998.
 
 
+</p>
 
 <!--    ACK   -->
 <section class="appendix">
--- a/glossary/respec-config.js	Thu Mar 22 15:05:31 2012 +0000
+++ b/glossary/respec-config.js	Mon Mar 26 11:11:03 2012 -0400
@@ -1,11 +1,11 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "ED",
-    publishDate:          "2012-03-15",
-    //copyrightStart:       "2010",
+    publishDate:          "2012-03-26",
+    //copyrightStart:       "2011",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/
-    shortName:            "gld-gloss",
+    shortName:            "gld-glossary",
     //subtitle:             "",
     // if you wish the publication date to be other than today, set this
     // publishDate:  "2009-08-06",
@@ -18,7 +18,7 @@
     diffTool:             "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
 
     // if there a publicly available Editor's Draft, this is the link
-    edDraftURI:           "http://dvcs.w3.org/hg/gld/gld-gloss/",
+    edDraftURI:           "http://dvcs.w3.org/hg/gld/gld-glossary/",
 
     // if this is a LCWD, uncomment and set the end of its review period
     // lcEnd: "2009-08-05",
@@ -33,7 +33,7 @@
     // only "name" is required
     editors:  [
 			{ name: "David Wood", url: "http://3roundstones.com/about-us/leadership-team/david-wood/",  company: "3 Round Stones", companyURL: "http://3roundstones.com/"},
-        		{ name: "Bernadette Hyland", url: "https://twitter.com/bernhyland",  company: "3 Round Stones", companyURL: "http://3roundstones.com/"},
+        		{ name: "Bernadette Hyland", url: "http://3roundstones.com/about-us/leadership-team/bernadette-hyland/",  company: "3 Round Stones", companyURL: "http://3roundstones.com/"},
 		{ name: "Ghislain Atemezing", url: "http://www.eurecom.fr/~atemezin",  company: "INSTITUT TELECOM, Eurecom", companyURL: "http://www.eurecom.fr"}
     ],