--- a/glossary/index.html Mon Mar 26 11:19:13 2012 -0400
+++ b/glossary/index.html Mon Mar 26 12:00:33 2012 -0400
@@ -41,11 +41,15 @@
The part if the application that uses the content of an RDF store in an interaction with some user.
</section>
-<section >
+<section>
<h4>Blank Nodes</h4>
RDF nodes that have no URI and thus cannot be referenced globally. They are used to stand in for anonymous entities.
</section >
+<section>
+<h4>CC-BY-SA License</h4>
+Work available under a <a href="http://creativecommons.org/licenses/by-sa/3.0/" taget="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 id="close">
<h4>Closed World</h4>
The presumption that what is not known to be true must be false. The assumption underlying relational databases, most forms of logical programming, OWL DL and OWL Lite.
@@ -58,7 +62,7 @@
<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>.
+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 >
@@ -77,11 +81,6 @@
</section >
<section >
-<h4>Data Cloud</h4>
-<p class="todo">@@TODO: Define@@</p>
-</section >
-
-<section >
<h4>Data Hub</h4>
The <a href="http://thedatahub.org/">Data Hub</a> is a community-run catalogue of useful sets of data on the Internet, powered using an open-source data cataloguing software called <a href="http://ckan.org/">CKAN</a>. It is an openly editable open data catalogue, in the style of Wikipedia.
</section >
@@ -167,22 +166,22 @@
<section>
<h4>Linked Data</h4>
-It refers to a set of best practices for publishing and interlinking structured data on the Web.
-</section>
-
-<section>
-<h4>Knowledge Extraction</h4>
-It is the creation of knowledge from structured (relational databases, XML) and unstructured (text, documents, images) sources. The resulting knowledge needs to be in a machine-readable and machine-interpretable format and must represent knowledge in a manner that facilitates inferencing.
-</section>
-
-<section>
-<h4>Knowledge Discovery</h4>
-It describes the process of automatically searching large volumes of data for patterns that can be considered knowledge about the data.
+Refers to a set of best practices for publishing and interlinking structured data for access by both humans and machines via the use of the RDF family of syntaxes (e.g., RDF/XML, N3, Turtle and N-Triples) and HTTP URIs. Linked Data can be published by an person or organization behind the firewall or on the public Web. If Linked Data is published on the public Web, it is generally called <em>Linked Open Data</em>.
</section>
<section>
<h4>Linked Open Data</h4>
- A pattern for hyper-linking machine-readable data sets to each other using Semantic Web techniques, especially via the use of RDF and URIs. Enables distributed SPAQL queries of the data sets and a “browsing” or “discovery” approach to finding information (as compared to a search strategy.
+Refers to Linked Data published on the public Web. Publishing Linked Open Data enables distributed SPAQL queries of the data sets and a “browsing” or “discovery” approach to finding information, as compared to a search strategy.
+</section>
+
+<section>
+<h4>Linked Open Data Cloud</h4>
+The Linked Data Cloud represents datasets that have been published as Linked Data on the public Web.
+</section >
+
+<section>
+<h4> Linked Open Data Cloud diagram</h4>
+Refers to the pictoral depiction of the <a href=" http://lod-cloud.net/ target="blank">Linked Data Cloud</a>. There are various depictions of the Linked Open Data Cloud including color-by-theme describing the various data domains including government, geographic, publications, life sciences and media content. The Linked Open Data Cloud diagrams are maintained by <span rel="dc:creator"><a typeof="foaf:Person" href="http://richard.cyganiak.de/#me" property="foaf:name">Richard Cyganiak</a></span> (<a href="http://www.deri.ie/">DERI, NUI Galway</a>) and <span rel="dc:contributor"><a typeof="foaf:Person" href="http://www.wiwiss.fu-berlin.de/en/institute/pwo/bizer/team/JentzschAnja.html" resource="#anja" property="foaf:name">Anja Jentzsch</a></span> (<a href="http://www.wiwiss.fu-berlin.de/en/institute/pwo/bizer/">Freie Universität Berlin</a>).
</section>
<section>
@@ -191,11 +190,6 @@
</section>
<section>
-<h4>Linked Open Data Cloud</h4>
-Linked Open Data that has been published is depicted in a LOD cloud diagram. The diagram shows connections between linked data sets and color codes them based on data type (e.g., government, media, life sciences, etc.). The diagram can be viewed at: <a href="http://richard.cyganiak.de/2007/10/lod/" target="blank">Linking Open Data cloud diagram, by Richard Cyganiak and Anja Jentzsch.</a>
-</section>
-
-<section>
<h4>Machine-Readable Cataloging system</h4>
A family of formats for the representation of bibliographic information in libraries (ISO 2709, ANSI/NISO Z39.2).
</section>
@@ -295,17 +289,17 @@
<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>.
+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>.
+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.
+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>