fix all broken links
authorSandro Hawke <sandro@hawke.org>
Mon, 27 May 2013 12:44:57 -0400
changeset 527 95e4f5b05a2d
parent 526 d4e0c2501ab0
child 528 efd8f3a80135
fix all broken links
glossary/index.html
glossary/respec-ref.js
--- a/glossary/index.html	Sun May 26 12:32:42 2013 +0100
+++ b/glossary/index.html	Mon May 27 12:44:57 2013 -0400
@@ -65,7 +65,7 @@
 
 <section>
 <h4>Closed World</h4>
-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>.
+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.
 </section>
 
 <section >
@@ -120,7 +120,7 @@
 
 <section>
 <h4>Data Market</h4>
-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.
+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>
@@ -245,7 +245,7 @@
 
 <section>
 <h4>HTTP URIs</h4>
-See <a href="uniform-resource-identifier">Uniform Resource Identifier</a>.
+See <a href="#uniform-resource-identifier">Uniform Resource Identifier</a>.
 </section>
 
 <section>
@@ -461,12 +461,12 @@
 
 <section>
 <h4>RDF</h4>
-See <a href="#resource-description-framework">Resource Description Framework</a>
+See <a href="#resource-description-framework-rdf">Resource Description Framework</a>
 </section>
 
 <section>
 <h4>RDFa</h4>
-See <a href="#resource-description-framework-attributes">Resource Description Framework Attributes</a>
+See <a href="#resource-description-framework-in-attributes-rdfa">Resource Description Framework in Attributes</a>
 </section>
 
 <section>
@@ -506,7 +506,7 @@
 
 <section>
 <h4>Resource Description Framework (RDF)</h4>
-A family of international standards for data interchange on the Web produced by W3C.  Resource Description Framework (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. See also [<a href="http://www.w3.org/TR/rdf11-concepts/">RDF 1.1 Concepts and Abstract Syntax</a>
+A family of international standards for data interchange on the Web produced by W3C.  Resource Description Framework (RDF) is based on the idea of identifying things using Web identifiers or <a href="#uri">HTTP URIs</a>, and describing resources in terms of simple properties and property values. See also [<a href="http://www.w3.org/TR/rdf11-concepts/">RDF 1.1 Concepts and Abstract Syntax</a>
 </section>
 
 <section>
@@ -521,12 +521,12 @@
 
 <section>
 <h4>REST</h4>
-See <a href="#representational-state-transfer">Representational State Transfer</a>
+See <a href="#representational-state-transfer-rest">Representational State Transfer</a>
 </section>
 
 <section>
 <h4>REST API</h4>
-An application programming interface (API) implemented using HTTP and the principles of REST to allow actions on Web resources.  The most common actions are to create, retrieve, update and delete resources.  See also <a href="#representational-state-transfer">Representational State Transfer</a>.
+An application programming interface (API) implemented using HTTP and the principles of REST to allow actions on Web resources.  The most common actions are to create, retrieve, update and delete resources.  See also <a href="#representational-state-transfer-rest">Representational State Transfer</a>.
 </section>
 
 <section>
@@ -622,7 +622,7 @@
 
 <section >
 <h4>Uniform Resource Identifier</h4>
-A global identifier standardized by joint action of the World Wide Web Consortium and Internet Engineering Task Force.  A Uniform Resource Identifier (URI) may or may not be resolvable on the Web. 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 such as colors.  See also <a href="#information-resource-identifier">Information Resource Identifier</a> and <a href="#uniform-resource-locator">Uniform Resource Locator</a>.  See also Uniform Resource Identifier (URI): Generic Syntax [[!RFC3986]] and <a href="http://www.w3.org/DesignIssues/Architecture.html" target="_blank">http://www.w3.org/DesignIssues/Architecture.html</a>.
+A global identifier standardized by joint action of the World Wide Web Consortium and Internet Engineering Task Force.  A Uniform Resource Identifier (URI) may or may not be resolvable on the Web. 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 such as colors.  See also <a href="#internationalized-resource-identifier">Internationalized Resource Identifier (IRI)</a> and <a href="#uniform-resource-locator">Uniform Resource Locator (URL)</a>.  See also Uniform Resource Identifier (URI): Generic Syntax [[!RFC3986]] and <a href="http://www.w3.org/DesignIssues/Architecture.html" target="_blank">http://www.w3.org/DesignIssues/Architecture.html</a>.
 </p>
 <p>
 URIs have been known by many names: Web addresses, Universal Document Identifiers, Universal Resource Identifiers.  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>. See also Uniform Resource Identifier (URI): Generic Syntax [[!RFC3986]].
--- a/glossary/respec-ref.js	Sun May 26 12:32:42 2013 +0100
+++ b/glossary/respec-ref.js	Mon May 27 12:44:57 2013 -0400
@@ -44,7 +44,7 @@
 		berjon.biblio["N3"] = "<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>";
 		berjon.biblio["RDF-CONCEPTS"] = "<cite><a href=\"http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/\">Resource Description Framework (RDF): Concepts and Abstract Syntax</a></cite>, Graham Klyne, Jeremy J. Carroll,  10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/\">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/</a>";		
 		
-		berjon.biblio["RDF11-CONCEPTS"] = "<cite><a href=\"http://www.w3.org/TR/rdf11-concepts/#resources-and-statements/\">RDF 1.1: Concepts and Abstract Syntax</a></cite>, Richard Cyganiak, David Wood, 15 January 2013. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/rdf11-concepts/#resources-and-statements/\">http://www.w3.org/TR/rdf11-concepts/#resources-and-statements/</a>";		
+		berjon.biblio["RDF11-CONCEPTS"] = "<cite><a href=\"http://www.w3.org/TR/rdf11-concepts\">RDF 1.1: Concepts and Abstract Syntax</a></cite>, Richard Cyganiak, David Wood, 15 January 2013. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/rdf11-concepts\">http://www.w3.org/TR/rdf11-concepts</a>";		
 		
 		berjon.biblio["RFC4627"] = "<cite><a http://www.ietf.org/rfc/rfc4627.txt\">The application/json Media Type for JavaScript Object Notation (JSON)</a></cite>, D. Crockford,   July 2006. Network Working Group. URL: <a href=\"http://www.ietf.org/rfc/rfc4627.txt\">http://www.ietf.org/rfc/rfc4627.txt</a>";