added turtle to biblio
authoratemezin
Fri, 08 Mar 2013 12:41:50 +0100
changeset 362 e8b78d300e6e
parent 361 2afab275cc4a
child 363 b271e8dd1a89
added turtle to biblio
glossary/index.html
glossary/index.html~
glossary/respec-ref.js
glossary/respec-ref.js~
--- a/glossary/index.html	Fri Mar 08 01:46:25 2013 +0000
+++ b/glossary/index.html	Fri Mar 08 12:41:50 2013 +0100
@@ -513,7 +513,7 @@
 
 <section >
 <h4>Turtle</h4>
-An RDF serialization format designed to be easier to read than others such as RDF/XML.  Turtle allows an RDF graph to be written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. Turtle provides levels of compatibility with the existing N-Triples format as well as, the triple pattern syntax of the SPARQL W3C Recommendation. See W3C <a href="http://www.w3.org/TR/turtle/">Terse RDF Triple Language</a> documentation.
+An RDF serialization format designed to be easier to read than others such as RDF/XML.  Turtle allows an RDF graph to be written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. Turtle [[!TURTLE-TR]] provides levels of compatibility with the existing N-Triples format as well as, the triple pattern syntax of the SPARQL W3C Recommendation. 
 </section >
 
 <section >
--- a/glossary/index.html~	Fri Mar 08 01:46:25 2013 +0000
+++ b/glossary/index.html~	Fri Mar 08 12:41:50 2013 +0100
@@ -1,14 +1,17 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN"
                       "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
+ 
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
-	<title>Government Linked Data Glossary</title>
-	<meta name="description" content="Government Linked Data Glossary" />
+	<title>Linked Data Glossary</title>
+	<meta name="description" content="Linked Data Glossary" />
 	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-	<script type="text/javascript"src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+	<script type="text/javascript" src='../respec/respec3/builds/respec-w3c-common.js' class='remove'></script>
 	<script src="respec-ref.js"></script>
 	<script src="respec-config.js"></script>
+	<script type="text/javascript" src="../respec/gld-bib.js" class="remove"></script>
+  	   
 	<link rel="stylesheet" type="text/css" href="local-style.css" />
 </head>
 <body>
@@ -16,270 +19,587 @@
 
 <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>
-<p class="todo">@@TODO EXPAND MORE @@</p>
+<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 Practices for Publishing Linked Data</a> document published by the <a href="http://www.w3.org/2011/gld/charter">W3C Government Linked Data Working Group</a>. This glossary is intended for publishers new to publishing data using a Linked Data approach, as well as seasoned information professionals publishing to the Web of Data.  A Linked Data approach involves explicitly defining relationships between data elements.  Linked Data depends on the use of shared or common vocabularies that describe concepts and relationships (also referred to as "terms") to describe and represent a given topic.
 </section>
 
 <section id="sotd">
-
 </section>
 
 <section class="introductory">
 <h2>Scope</h2>
-
 <p>
-This document is aimed at assisting government IT managers, procurement officers, Web developers, vendors, and researchers who are interested in publishing open government data using W3C standards.  The benefits of using international standards for data exchange is to significantly increase interoperability of data.
-</p>
-<p>
-Readers of this document are expected to be familiar with delivery of content via the Web, and to have a general familiarity with the technologies involved, but are not required to have a background in semantic technologies or previous experience with Linked Data. Data stewards, curators, database administrators and other personnel involved in Open Government initiatives are encouraged to read this Linked Open Data Best Practices document. 
+This glossary lists terms related to Linked Data.  Linked Open Data is a set of techniques for the publication of structured data on the public Web using standard formats and interfaces.  Linked Open Data also refers to data that conforms to those techniques.  Linked Data is comprised of data described using HTTP URIs (uniform resource identifiers which are the foundation of the Web.  Developers can query Linked Data from multiple sources at once and combine data dynamically on the Web.</p>
 </section>
 
-<section id="definitions">
-<h2> Definition </h2>
-<p class="todo"> @@TODO: add links to W3C documents, and new terms to the actual glossary @@</p>
-<h4 id="abox"> 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>
+<h4>Apache License</h4>
+A popular Open Source license published by the Apache Software Foundation.  <a href="http://www.apache.org/licenses/LICENSE-2.0.html"> Apache License, version 2.0</a> is used for many Linked Data tools and projects. 
+</section>
 
-<h4>Application Programmer Interface(API)</h4>
-An abstraction implemented in software that defines how others should make use of a software package such as a library or other reusable program.
-
+<section>
+<h4>API</h4>
+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>
 
-<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.
+<section>
+<h4>Application Interface</h4>
+The part if the application that uses the content of a database in a consistent manner with a developer.
+</section>
 
-<h4>Controlled vocabularies</h4>
+<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>
+
+<section>
+<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.
+</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>
 
+<section>
+<h4>Converter</h4>
+A tool or scripts that converts data from some form (e.g., spreadsheet) into Resource Description Framework (RDF).  Publishing good quality, useful RDF requires expression of the relationships using Linked Data modeling subject matter expertise.  Thus, modeling about the relationships implicit in the data must be performed before the data is converted from one format into RDF. 
+</section>
+
+<section>
+<h4>CSV</h4>
+A CSV (comma separated values) 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" on the data scale 
+</section>
+
+<section>
+<h4>D2RQ</h4>
+D2RQ may be used to describe a mapping language definition or an Open Source platform project.  
+</section>
+
+<section>
+<h4>D2RQ Platform</h4>
+A system for accessing relational databases as virtual, read-only RDF graphs. It offers RDF-based access to the content of relational databases without having to replicate it into an RDF store. The D2RQ Platform allows one to query a non-RDF database using SPARQL, access the content of the database as Linked Data over the Web, create custom dumps in RDF formats for loading into an RDF triplestore, and access information in a non-RDF database using the Apache Jena API.  See the <a ref="http://d2rq.org/">D2RQ Open Source Project</a>.
+</section>
+
+<section>
+<h4>D2RQ Mapping Language</h4>
+A declarative lanugage for mapping relational database schemas to RDF vocabularies and OWL ontologies.  The language is implmented in the D2RQ Platform.  See the <a href="http://d2rq.org/d2rq-language">D2RQ Mapping Language</a> description.
+</section>
+
+<section >
 <h4>Database to RDF Queueing</h4>
 A mechanism to query information in traditional management systems such as relational databases via the SPARQL query language.  D2RQ may refer to the language definition or the Open Source Software project.
+</section >
 
-<h4>Data Catalogue</h4>
-<p class="todo">@@TODO: [email protected]@</p>
+<section >
+<h4>Data Cloud</h4>
+Also refered to <a href="http://richard.cyganiak.de/2007/10/lod/">Linked Data Cloud</a>  is visual representation of datasets published in Linked Data format, using metadata generated by a given directory (e.g: CKAN) where the datasets are organized by domain, with outgoing links to external datasets. 
+</section >
 
-<h4>Data Cloud</h4>
-<p class="todo">@@TODO: [email protected]@</p>
-
+<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 >
 
-
+<section>
 <h4>Data Market</h4>
-<p class="todo">@@TODO: [email protected]@</p>
+A portal where a community can upload and share data in various ways, such as dump files, endpoint access or API access.
+It could also contain some applications making use of the datasets.
+</section >
 
+<section>
+<h4>Data Warehouse</h4>
+A storage and retrieval system for enterprise information designed to centralize information from other stores to facilitate cross-system querying and reporting.  Linked Data is an alternative to data warehouses whereby data consumers (human and machine) assume a distributed information architecture and use HTTP URIs to describe and access resources.
+</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.
-
-<h4>Directed Acyclic Graph</h4>
+</section >
 
-A directed graph (like RDF) with the additional restriction that no loops or cycles are permitted.  A cycle is a path from a given node that would allow one to find their way back to the starting node.
+<section>
+<h4>Dereferencing a URI</h4>  
+The act of retrieving a representation of a resource or the semantic description of a resource created by the URI owner.  A URI was successfully dereferenced when an agent successfully retrieved the representation of the resource or received the semantic description of a resource via the protocol specified within the URI.
+</section>
 
-<h4 id="dgraph">Directed Graph</h4>
+<section>
+<h4>Descriptor Resource</h4> 
+A type of resource that bears/carries the description of a Subject.</h4>
+</section>
 
+<section>
+<h4>DCAT</h4>
+DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. See <a href="http://www.w3.org/TR/vocab-dcat/">Data Catalog Vocabulary (DCAT)</a> documentation.
+</section>
+
+<section>
+<h4>Directed Graph</h4>
 A graph in which the links between nodes are directional (they only go from one node to another).  RDF represents things (nouns) and the relationships between them (verbs) in a directed graph.  In RDF, the links are differentiated by being assigned URIs.
+</section>
 
+<section>
 <h4>Document Type Definition</h4>
 A type of schema for defining a markup language, such as in XML or HTML (or their predecessor SGML).
+</section>
 
+<section>
 <h4>Domain Name System</h4> The Internet's mechanism for mapping between a human-readable host name (e.g. www.example.com) and an Internet Protocol (IP) Address (e.g. 203.20.51.10).
+</section>
 
+<section>
 <h4>Dublin Core Element Set</h4>
- A vocabulary of fifteen properties for use in resource descriptions, such as may be found in a library card catalog (author, publisher, etc).  The most commonly used vocabulary for Semantic Web applications.
+ A vocabulary of fifteen properties for use in resource descriptions, such as may be found in a library card catalog (creator, publisher, etc).  The Dublin Core Elecment Set is the most commonly used vocabulary for Linked Data applications.  <a href="See http://dublincore.org/documents/dcmi-terms/"> Dublin Core Element Set, Version 1.1 Specification</a>
+</section>
 
+<section>
 <h4>Dublin Core Metadata Initiative</h4> 
-An open international organization engaged in the development of interoperable metadata standards, including the Dublin Core Element Set.
+An open international organization engaged in the development of interoperable metadata standards, including the Dublin Core Element Set.  <a href="http://dublincore.org/about-us/">The Dublin Core Metadata Initiative (DCMI)</a> supports metadata design and best practices across a broad range of purposes and business models.
+</section>
 
+<section>
+<h4>Entity</h4>
+Anything that can be named using an HTTP URL and serve as the Subject of a description.
+</section>
+
+<section>
+<h4>ETL</h4>
+ETL is an abbreviation for extact, transform, load.  Used in the Linked Data context to mean pull data from a database (often a relational database), transform to a Linked Data serialization, and load it into an RDF database.
+</section>
+
+<section>
 <h4>Free/Libre/Open Source Software</h4>
  A generic and internationalized term for software released under an Open Source license.
-
+</section>
 
+<section>
 <h4>Graph</h4>
-A collection of objects (represented by "nodes") any of which may be connected by links between them.  See also<a href="#dgraph">Directed Graph</a>.
+A collection of objects (represented by "nodes") any of which may be connected by links between them.  See also<a href="#directed-graph"> Directed Graph</a>.
+</section>
 
+<section>
+<h4>Hash URI Strategy</h4>
+The hash URI strategy builds on the characteristic that URIs may contain a special part that is separated from the base part of the URI by a hash symbol (#). This special part is called the fragment identifier.
+</section>
+
+<section>
 <h4>Hypertext Markup Language</h4> 
 The predominant markup language for hypertext pages on the Web.  HTML defines the structure of Web pages. A family of W3C standards.
+</section>
 
+<section>
 <h4>Hypertext Transfer Protocol</h4> 
 The standard transmission protocol used on the World Wide Web to transfer hypertext requests and information between Web servers and Web clients (such as browsers). An IETF standard.
+</section>
 
+<section>
 <h4>International Standards Organization</h4> 
 A network of the national standards institutes of 162 countries that cooperate to define international standards.  It Defines many standards including in the context  formats for dates and currency.
+</section>
 
+<section>
 <h4>Internet Engineering Task Force</h4>
  An open international community concerned with the evolution of Internet architecture and the operation of the Internet. Defines standards such as HTTP and DNS.
+</section>
 
+<section>
+<h4>Inference</h4>
+To infer something is to create a new relationship.  Using Linked Data, existing relationships are modeled as a set of (named) relationships between resources.  Linked Data helps humans and machines to find new relationships through automatic procedures that generate new relationships based on the data and based on some additional information in the form of a vocabulary.
+</section>
+
+<section>
+<h4>JSON</h4>
+JavaScript Object Notation (JSON) is syntax for storing and exchanging text based information.  JSON has proven to be a highly useful and popular object serialization and messaging format for the Web. 
+</section>
+
+<section>
+<h4>JSON-LD</h4>
+JSON-LD (JavaScript Object Notation for Linking Data) is an attempt to harmonize the representation of Linked Data in JSON.  JSON-LD is a specification that outlines a common JSON representation format for expressing directed graphs, mixing both Linked Data and non-Linked Data in a single document.  JSON-LD is a lightweight Linked Data format that provides data context. <a href="http://json-ld.org/spec/FCGS/json-ld-syntax/20120626/"> JSON-LD Syntax</a> is easy for humans to read and write as well as, easy for machines to parse and generate. JSON-LD is based on the JSON format and provides a way to allow JSON data interoperate at Web-scale.  JSON-LD is an appropropriate Linked Data interchange language for JavaScript environments, Web service and NoSQL databases. 
+</section>
+
+<section>
 <h4>Jena</h4>
  An Open Source Software implementation of a Semantic Web development framework.  Jena supports the storage, retrieval and analysis of RDF information. 
-
+</section>
 
+<section>
+<h4>Linked Data</h4>
+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 Data client</h4>
+A client side application that consumes Linked Data using standard Web techniques.  A Linked Data Client may resolve URI's to retrieve Linked Data serializations, using appropriate content negotiation, and understands how to make use of those representations once it receives them.  A Linked Data client understands standard REST API, for example the Linked Data REST API.  There are many examples of Linked Data clients, several include: Tim Berners-Lee's early <a href="http://www.w3.org/2005/ajar/tab.html"> Tabulator browser</a>, <a href="http://www.visualdataweb.org/gfacet.php"> gFacet</a>, and the <a href="http://callimachusproject.org/docs/1.0/articles/callimachus-shell.docbook?view">Callimachus Shell (CaSH)</a>.
+</section>
+
+<section>
 <h4>Linked Open Data</h4>
-Linked Open Data: 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>
 <h4>Linking Government Data</h4> 
 The use of tools and techniques of the Semantic Web to connect, expose and use data from government systems.
+</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>
 <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>
 
+<section>
 <h4>Management, Resources and Results Structure</h4> 
 Government of Canada policy linking the management of government resources and program results to their organizational structures. It provides a representation of how a department is managed through a)  strategic outcomes; b) program activity architecture (PAA); and c)  governance structure. 
+</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>
 
+<section>
 <h4>Metadata Object Description Schema</h4>
  A bibliographic description system intended to be a compromise between MARC and DC metadata.  Implemented in XML Schema (see DC, MARC, XSD).
-
-
-<h4 id="n3">Notation 3</h4> An RDF syntax intended to be readable by humans.  See also <a href="#ttl">Turtle</a>.
-
-
+</section>
 
-<h4 id="ontology"> Ontology</h4>
-A formal representation of relationships between items in a directed graph structure.  See <a href="#taxonomy">taxonomy</a>.
+<section>
+<h4>Modeling Process</h4>
+To produce high quality Linked Data, subject matter experts often work with developers to capture the context of data and define the relationships of the data.  Capturing organizational knowledge about the meaning of the data within the RDF data model means the data is more likely to be reused correctly. Well defined context ensures better understanding, proper reuse, and is critical when establishing linkages to other data sets. 
+</section>
 
-<h4> Ontology matching</h4>
+<section>
+<h4>N3</h4>
+Abbreviation for Notation3 (N3), a readable RDF syntax used for expressing assertion and logic.  N3 is a superset of RDF, extending the RDF model by adding formulae (literals which are graphs themselves), variables, logical implication, and functional predicates. See also <a href="#turtle">Turtle</a>.
+</section>
 
+<section>
+<h4>Namespace</h4>
+A set of names that belongs to a single authority. Namespaces allow different agents to use the same word in different ways.
+</section>
 
+<section>
+<h4 >Ontology</h4>
+A formal representation of relationships between items in a directed graph structure.  See <a href="#taxonomy">taxonomy</a>.
+</section>
 
+<section>
+<h4>Ontology Matching</h4>
+It is a process of finding correspondences between semantically related entities of the ontologies, which 
+can be used for various tasks, such as ontology merging, query answering, data translation, or for navigation on the semantic web. 
+</section>
+
+<section>
+<h4>Open Government Data</h4>
+Open government data broadly refers to content that is published on the public Web in a variety of non-proprietary formats including as XML, CSV and PDF.
+</section>
+
+<section>
 <h4>Open World</h4>
  The presumption that what is not known to be true may yet be true if additional information is later obtained.  The assumption underlying RDF and OWL Full.
-
-<h4>protocol</h4>
- A set of instructions for transferring data from one computer to another over a network.  A protocol standard defines both message formats and the rules for sending and receiving those messages.
-
-<h4>Public Sector Information</h4>
- Information created by a government in the course of governing.
-
+</section>
 
+<section>
+<h4>Predicate</h4>
+Modifies the Subject of an RDF Statement.  Inspired from work in predicate calculus, (also called predicate logic, first order logic), the predicate of a sentence can be thought of as the verb.
+</section>
+
+<section>
+<h4>Provenance</h4>
+Provenance refers to the sources of information, such as entities and processes, involved in producing or delivering an artifact.
+</section>
+
+<section>
+<h4>Protocol</h4>
+A set of instructions for transferring data from one computer to another over a network.  A protocol standard defines both message formats and the rules for sending and receiving those messages.
+</section>
+
+<section>
+<h4>Public Sector Information</h4>
+Information created by a government in the course of governing.
+</section>
+
+<section>
 <h4>Quad Store</h4>
- A colloquial phrase for an RDF database that stores RDF triples plus an additional element of information, often used to collect statements into groups.
+A colloquial phrase for an RDF database that stores RDF triples plus an additional element of information, often used to collect statements into groups.
+</section>
 
+<section>
+<h4>Query</h4>
+A query in the context of Linked Data implies programmatic retrieval of resources and their relationships from the Web of Data.  Using the SPARQL language, developers issue queries based on (triple) patterns.  SPARQL queries provide one or more patterns against such relationships.  To get results, the query engine retrieves a response matching the requested query, returning a query result set.  Results may be returned in a table format for example, which can be used to build complex mashups and visualizations.
+</section> 
+
+<section>
 <h4>Raw Data</h4>
-<p class="todo">@@TODO: [email protected]@</p>
+Machine-readable files from tje wilderness released without any specific effort to make them applicable to a particular application.  The advantage of "raw" data is that it can be reused in multiple applications created by multiple communities; but this requires some means of processing it.
+</section>
 
-<h4>RDF (Resource Description Framework)</h4>
- A language for representing information about resources in the World Wide Web. RDF is based on the idea of identifying things using Web identifiers (called Uniform Resource Identifiers, or URIs), and describing resources in terms of simple properties and property values. This enables RDF to represent simple statements about resources as a graph of nodes and arcs representing the resources, and their properties and values [[!RDF-Primer]].
+<section>
+<h4>Resource</h4>
+Anything that can be addressed by a URI.
+</section>
 
+<section>
+<h4>RDF</h4>
+Resource Description Framework (RDF), is a general-purpose language for representing information in the Web.  RDF is based on the idea of identifying things using Web identifiers or HTTP URIs (Uniform Resource Identifiers), and describing resources in terms of simple properties and property values. This enables RDF to represent simple statements about resources as a graph of nodes and arcs representing the resources, and their properties and values [[!RDF-Primer]].
+</section>
+
+<section>
+<h4>RDFa</h4>
+A system for embedding RDF data in a web page.
+</section>
+
+<section>
 <h4>RDF Database</h4>
  A type of database designed specifically to store and retrieve RDF information.
+</section>
 
+<section>
+<h4>RDF-JSON</h4>
+A concrete syntax in JavaScript Object Notation (JSON) ([RFC4627]) for RDF as defined in the RDF Concepts and Abstract Syntax ([RDF-CONCEPTS]) W3C Recommendation.  An RDF-JSON document serializes such a set of RDF triples as a series of nested data structures.  <a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-json/index.html"> RDF 1.1  JSON Serialization W3C Recommendation</a>
+</section>
+
+<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).  <a href="http://www.w3.org/TR/rdf-schema/"> RDF Schema W3C Recommendation</a>
+</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>
+<h4>REST</h4>
+REST (Representational State Transfer) is a style of software architecture for distributed systems that describes six constraints: uniform interface, stateless, cacheable, client-server, layered system, and code on demand (optional).  REST is the foundation of the World Wide Web and the dominant Web service design model.
+</section>
+
+<section>
+<h4>REST API</h4>
+An application program interface based on Representational State Transfer (REST).
+</section>
+
+<section>
 <h4>Schema</h4>
  A data model that represents the relationships between a set of concepts.  Some types of schemas include relational database schemas (which define how data is stored and retrieved), taxonomies and ontologies. 
+</section>
 
+<section>
 <h4>Semantic Technologies</h4>
  The broad set of technologies that related to the extraction, representation, storage, retrieval and analysis of machine-readable information. The Semantic Web standards are a subset of semantic technologies and techniques. 
+</section>
 
+<section>
 <h4> Semantic Web</h4>
  An evolution or part of the World Wide Web that consists of machine-readable data in RDF and an ability to query that information in standard ways (e.g. via SPARQL)
+</section>
 
+<section>
 <h4>Semantic Web Standards</h4>
  Standards of the World Wide Web Consortium (W3C) relating to the Semantic Web, including RDF, RDFa, SKOS and OWL. 
+</section>
 
+<section>
 <h4>Semantic Web Search Engine</h4>
-<p class="todo">@@TODO: [email protected]@</p>
+A search engine capable of making use of semantic technologies both to model its knowledge base and the content delivered to the users.
+</section>
 
+<section>
 <h4>Service Oriented Architecture</h4> 
 A set of architectural design guidelines used to expose services, often as Web Services.
-
-<h4>Sesame</h4> An Open Source Software implementation of a Semantic Web development framework.  Supports the storage, retrieval and analysis of RDF information. <a href="http://www.openrdf.org">See</a>
+</section>
 
-<h4>Silk</h4>
+<section>
+<h4>Sesame</h4> An Open Source Software implementation of a Semantic Web development framework.  Supports the storage, retrieval and analysis of RDF information. <a href="http://www.openrdf.org">See</a>
+</section>
 
-Silk(Silk Link Discovery Framework) is a tool for discovering relationships between data items within different Linked Data sources.
-
+<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>
 
+<section>
 <h4>SPARQL</h4>
- Simple Protocol and RDF Query Language (SPARQL) defines a standard query language and data access protocol for use with the Resource Description Framework (RDF) data model.Just as SQL is used to query relational data, SPARQL is used to query graph, or linked, data.
+Simple Protocol and RDF Query Language (SPARQL) defines a standard query language and data access protocol for use with the RDF.  Just as SQL is used to query relational data, SPARQL is used to query an RDF database.
+</section>
 
+<section>
+<h4>SPARQL client</h4>
+An application that can construct and issue a SPARQL query.  An example of a SPARQL client is <a href="http://jena.apache.org/documentation/query/index.html">ARQ</a>, part of the Apache Jena Project.  ARQ is a query engine for Jena that supports the SPARQL RDF Query Language.
+</section>
+
+<section>
+<h4>SPARQL endpoint</h4>
+An application that can answer a SPARQL query, including one where the native encoding of information is not in RDF.
+</section>
+
+<section>
 <h4>Structured Query Language</h4> 
 A query language standard for relational databases.
+</section>
 
+<section>
+<h4>Subject</h4>
+Who or what the RDF statement is about.
+</section>
 
+<section >
 <h4>Taxonomy</h4>
  A formal representation of relationships between items in a hierarchical structure.  See <a href="#ontology">ontology</a>.
+</section >
 
-<h4 id="tbox">Tbox</h4>
+<section >
+<h4 >Tbox</h4>
 One of two types of statements in an ontology (the other being <a href="#abox">Abox</a>).  Tbox statements describe a knowledge system in terms of controlled vocabularies (or "terminology", hence the "T"), e.g. A Person is a Mammal.
+</section >
 
+<section >
 <h4>Term</h4>
  A term is an entry in a controlled vocabulary, schema, taxonomy or ontology.
+</section >
 
+<section >
 <h4>Triple</h4>
- An RDF statement, consisting of two things (a "subject" and an "object") and a relationship between them (a verb, or "predicate").  This subject-predicate-object triple forms the smallest possible RDF graph (although most RDF graphs consist of many statements).
+ An RDF statement, consisting of two things (a "Subject" and an "Object") and a relationship between them (a verb, or "Predicate").  This subject-predicate-object triple forms the smallest possible RDF graph (although most RDF graphs consist of many statements).
+</section >
 
+<section >
 <h4>Triple store</h4>
  A colloquial phrase for an RDF database that stores RDF triples.
+</section >
 
+<section >
 <h4>Tuple</h4>
  An ordered list of elements.  RDF statements are 3-tuples; an ordered list of three elements.
+</section >
 
-<h4 id="ttl">Turtle</h4>
- An RDF serialization format, designed to be easier to read than others such as RDF/XML.  It is also a subset of <a href="#n3">N3</a>.
+<section >
+<h4>Turtle</h4>
+An RDF serialization format designed to be easier to read than others such as RDF/XML.  Turtle allows an RDF graph to be written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. Turtle provides levels of compatibility with the existing N-Triples format as well as, the triple pattern syntax of the SPARQL W3C Recommendation. See W3C <a href="http://www.w3.org/TR/turtle/">Terse RDF Triple Language</a> documentation.
+</section >
 
+<section >
 <h4>Uniform Resource Indicator</h4>
- A global identifier for the Web standardized by joint action of the W3C and IETF.  A URI may or may not be resolvable on the Web (see <a href="#url">URL</a>).
+ A global identifier for the Web standardized by joint action of the W3C and IETF.  A URI may or may not be resolvable on the Web (see <a href="#uniform-resource-locator">URL</a>).
+</section >
 
+<section>
 <h4>Universally Unique Identifier</h4>
  A large hexadecimal number that may be calculated by anyone without significant central coordination and used to uniquely identify a resource.  A standard of the Open Software Foundation.
-
-<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. 
-
+</section>
 
-<h4 id="url">Uniform Resource Locator</h4>
- A global identifier for Web resources standardized by joint action of the W3C and IETF.  A URL is resolvable on the Web and is commonly called a "Web address".
+<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, 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, 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 >
 
-<h4>Virtuoso</h4>
-<p class="todo">@@TODO: [email protected]@</p>
+<section>
+<h4>URIs dereferenceable</h4>
+It means that HTTP clients can look up the URI using the HTTP protocol and retrieve a description of the resource that is identified by the URI. This
+applies to URIs that are used to identify classic HTML documents, as well as URIs that are used in the Linked Data context to identify real-world objects and abstract concepts.
+</section>
 
+<section>
+<h4>Uniform Resource Locator</h4>
+A global identifier for Web resources standardized by joint action of the W3C and IETF.  A URL is resolvable on the Web and is commonly called a "Web address".
+</section>
+
+<section>
+<h4>Vocabulary</h4>
+A vocabulary defines the concepts and relationships (also referred to as "terms")  to describe and represent a given topic.  A vocabulary is used to classify the terms that are used for a particular application, characterize relationships, and define possible constraints on the use of the terms.  Vocabularies can range from simple such as the widely used Dublin Core Vocabulary to the very complex with thousands of terms, such as those used in healthcare to describe symptoms, diseases and treatments.  Vocabularies play a very important role in Linked Data, specifically to help with data integration.  Vocabularies also help to organize knowledge and are extensively used by libraries, museums, newspapers and government agencies that manage large collections of data.
+</section>
+
+<section>
 <h4>Web 2.0</h4>
  A colloquial description of the part of the World Wide Web that implements social networking, blogs, user comments and ratings and related human-centered activities.
+</section >
 
+<section>
 <h4>Web 3.0</h4>
- A colloquial description of the part of the World Wide Web that implements machine-readable data and the ability to perform distributed queries and analysis on that data.  Considered synonymous with the phrases "Semantic Web" and "The Web of Data".
+A colloquial description of the part of the World Wide Web that implements machine-readable data and the ability to perform distributed queries and analysis on that data.  Considered synonymous with the phrases "Semantic Web" and "The Web of Data".
+</section>
 
-<h4>Web Ontology Language</h4>
+<section>
+<h4>Web of Data</h4>
+A phrase to describe publishing data sets using a Linked Data principles thereby making the World Wide Web into a global database.
+</section>
+
+<section>
+<h4>Web Ontology Language (OWL)</h4>
  A family of knowledge representation and vocabulary description languages for authoring ontologies, based on RDF and standardized by the W3C.  Standardized variants include OWL Full, OWL DL (for "description logic") and OWL Lite.
+</section >
 
+<section>
 <h4>World Wide Web Consortium</h4> 
 An international community that develops standards for the World Wide Web. Defines standards such as HTML, XML and RDF.
+</section >
 
+<section>
 <h4>eXtensible Hypertext Markup Language</h4> 
  A family of versions of HTML based on XML and standardized by the W3C.
+</section >
 
-<h4>eXtensible Markup Language</h4> 
+<section>
+<h4>eXtensible Markup Language (XHTML)</h4> 
  A specification for creating structured textual computer documents.  Many thousands of XML formats exist, including XHTML.  A family of standards from the W3C.
+</section >
 
+<section>
 <h4>XML Schema</h4> 
 Limitations on the content of an XML document that defines what structural elements are allowed.
-
-<h4>eXtensible Stylesheet Language Transformations</h4> 
- Declarative programs to transform one XML document into another XML document.
-
+</section >
 
-
-
+<section>
+<h4>eXtensible Stylesheet Language Transformations (XSLT)</h4> 
+Declarative programs to transform one XML document into another XML document.
 </section>
 
 
-
-
-
 <!--    ACK   -->
 <section class="appendix">
 <h2>Acknowledgments</h2>
-<p>The editors are very thankful for the contributions of David Wood and Springer.
+<p>The editors are very thankful for the glossary terms contributed from <a href="http://3roundstones.com/linking-government-data/">Linking Government Data</a> by David Wood, (<a href="http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-1-4614-1766-8">Springer 2011</a>).
+
 </p>
 </section>
 </body>
--- a/glossary/respec-ref.js	Fri Mar 08 01:46:25 2013 +0000
+++ b/glossary/respec-ref.js	Fri Mar 08 12:41:50 2013 +0100
@@ -14,6 +14,9 @@
                 berjon.biblio["XHTML-RDFA-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/html-rdfa-1.1\">HTML+RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 24 May 2011. URL: http://www.w3.org/profile/html-rdfa-1.1";
                 berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: http://www.w3.org/Protocols/rfc2616/rfc2616.html."; 
                 berjon.biblio["RFC2396"] = "<cite><a ref=\"http://tools.ietf.org/html/rfc2396\">Uniform Resource Identifiers (URI): Generic Syntax</a></cite>, Berners-Lee, T., Fielding, R.T., and L. Masinter.  August 1998. Internet RFC 2396. URL: http://tools.ietf.org/html/rfc2396";
+		 berjon.biblio["TURTLE-TR"] = "<cite><a ref=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">Turtle: Terse RDF Triple Language.</a></cite>, Eric Prud'hommeaux, Gavin Carothers.  19 February 2013. W3C Candidate Recommendation. URL: <a href=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\"></a>;
+
+
 
 
                 // process the document before anything else is done
--- a/glossary/respec-ref.js~	Fri Mar 08 01:46:25 2013 +0000
+++ b/glossary/respec-ref.js~	Fri Mar 08 12:41:50 2013 +0100
@@ -1,7 +1,8 @@
 var preProc = {
       apply:  function(c) {
                 // extend the bibliography entries
-		berjon.biblio["WEBARCH"] = "<cite><a href=\"http://www.w3.org/TR/webarch/\">Web architecture</a></cite>Ian Jacobs, Norman Walsh (Editors). 15 December 2004. W3C Recommendation. URL: http://www.w3.org/TR/webarch/ ";
+		berjon.biblio["PROV"] = "<cite><a href=\"http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/\">Provenance Final Report</a></cite> Yolanda Gil; et al.  08 December 2010. W3C Incubator Group Report. URL: http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/ ";
+		berjon.biblio["WEBARCH"] = "<cite><a href=\"http://www.w3.org/TR/webarch/\">Web architecture</a></cite> Ian Jacobs, Norman Walsh (Editors). 15 December 2004. W3C Recommendation. URL: http://www.w3.org/TR/webarch/ ";
 		berjon.biblio["RDF-Primer"] = "<cite><a href=\"http://www.w3.org/TR/rdf-primer/\">RDF-Primer</a></cite> Frank Manola, Eric Miller (Editors). 10 February 2004. W3C Recommendation. URL: http://www.w3.org/TR/rdf-primer/ ";
                 berjon.biblio["MICRODATA"] = "<cite><a href=\"http://www.w3.org/TR/microdata/\">Microdata</a></cite> Ian Hickson; et al. 04 March 2010. W3C Working Draft. URL: http://www.w3.org/TR/microdata/ ";
                 berjon.biblio["XHTML-RDFA"] = "<cite><a href=\"http://www.w3.org/TR/xhtml-rdfa/\">XHTML+RDFa</a></cite> Manu Sporny; et al. 31 March 2011. W3C Working Draft. URL: http://www.w3.org/TR/xhtml-rdfa/ ";
@@ -11,7 +12,12 @@
                 berjon.biblio["VOID-GUIDE"] = "<cite><a href=\"http://www.w3.org/TR/void/\">Describing Linked Datasets with the VoID Vocabulary</a></cite>, K. Alexander, R. Cyganiak, M. Hausenblas, and J. Zhao, W3C Interest Group Note 03 March 2011. URL: http://www.w3.org/TR/void/";
                 berjon.biblio["RDFA-CORE-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/rdfa-1.1\">RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 02 June 2011. URL: http://www.w3.org/profile/rdfa-1.1";
                 berjon.biblio["XHTML-RDFA-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/html-rdfa-1.1\">HTML+RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 24 May 2011. URL: http://www.w3.org/profile/html-rdfa-1.1";
-                berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: http://www.w3.org/Protocols/rfc2616/rfc2616.html."
+                berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: http://www.w3.org/Protocols/rfc2616/rfc2616.html."; 
+                berjon.biblio["RFC2396"] = "<cite><a ref=\"http://tools.ietf.org/html/rfc2396\">Uniform Resource Identifiers (URI): Generic Syntax</a></cite>, Berners-Lee, T., Fielding, R.T., and L. Masinter.  August 1998. Internet RFC 2396. URL: http://tools.ietf.org/html/rfc2396";
+		 berjon.biblio["TURTLE-TR"] = "<cite><a ref=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">Turtle: Terse RDF Triple Language.</a></cite>, Eric Prud'hommeaux, Gavin Carothers.  19 February 2013. W3C Candidate Recommendation. URL: http://www.w3.org/TR/2013/CR-turtle-20130219/";
+
+
+
 
                 // process the document before anything else is done
                 var refs = document.querySelectorAll('adef') ;