--- a/glossary/index.html Tue May 07 15:18:37 2013 -0400
+++ b/glossary/index.html Tue May 07 15:24:58 2013 -0400
@@ -328,13 +328,14 @@
</section>
<section>
-<h4>Machine Readable Data</h4>
-<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.
+<h4>Machine Readable Data</h4>
+<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.
-<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>
</section>
@@ -493,7 +494,7 @@
<section>
<h4>Resource Description Framework</h4>
-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</a>
+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>
@@ -524,12 +525,12 @@
<section>
<h4>Resource</h4>
-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>
<h4>Response</h4>
-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 [[RFC2616]] 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 [[RFC2616]] 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>
@@ -651,7 +652,7 @@
<h4>Uniform Resource Identifier</h4>
<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 W3C 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>
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," [[!RFC3986]]
</p>
</section >