--- a/glossary/index.html~ Thu May 09 17:36:19 2013 +0100
+++ b/glossary/index.html~ Thu May 16 14:59:40 2013 +0200
@@ -1,15 +1,13 @@
-<?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">
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+
<head>
<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='../respec/respec3/builds/respec-w3c-common.js' class='remove'></script>
- <script src="respec-ref.js"></script>
- <script src="respec-config.js"></script>
+ <script src="respec-ref.js" class='remove'></script>
+ <script src="respec-config.js" class='remove'></script>
<script type="text/javascript" src="../respec/gld-bib.js" class="remove"></script>
<link rel="stylesheet" type="text/css" href="local-style.css" />
@@ -18,7 +16,7 @@
<section id="abstract">
-<p> This document is a glossary of terms defined and used to describe Linked Data, and its associated vocabularies and <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html">Best Practices</a>. This document published by the <a href="http://www.w3.org/2011/gld/charter">W3C Government Linked Data Working Group</a> as a Working Group Note, is intended to help information management professionals, Web developers, scientists and the general public better understand publishing structured data using <a href="#linked-data-principles">Linked Data Principles</a>.
+<p> This document is a glossary of terms defined and used to describe Linked Data, and its associated vocabularies and <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html" target="_blank">Best Practices</a>. This document published by the <a href="http://www.w3.org/2011/gld/charter" target="_blank">W3C Government Linked Data Working Group</a> as a Working Group Note, is intended to help information management professionals, Web developers, scientists and the general public better understand publishing structured data using <a href="#linked-data-principles">Linked Data Principles</a>.
</section>
<section id="sotd">
@@ -32,7 +30,7 @@
<section>
<h4>5 Star Linked Data</h4>
-Tim Berners-Lee, the inventor of the Web and initiator of the <a href="http://linkeddata.org">Linked Data project</a>, suggested a 5 star deployment scheme for Linked Data. The 5 Star Linked Data system is cumulative. Each additional star presumes the data meets the criteria of the previous step(s).
+5 Star Linked Data refers to an incremental framework for deploying data. Tim Berners-Lee, the inventor of the Web and initiator of the <a href="http://linkeddata.org" target="_blank">Linked Data project</a>, suggested a 5 star deployment scheme for Linked Data. The 5 Star Linked Data system is cumulative. Each additional star presumes the data meets the criteria of the previous step(s).
<p class="highlight">☆ <b>Data is available on the Web, in whatever format.</b>
</p>
@@ -49,7 +47,7 @@
<p class="highlight">☆☆☆☆☆ <b>All of the above and links to other Linked Open Data.</b>
</p>
<p>
-An easy to read graphic for explaining the 5 Star Linked Data model may be seen on the <a href="http://www.cafepress.com/w3c_shop">5 Star Linked Open Data mug</a>. One reads both green labels for <a href="#linked-open-data">Linked Open Data</a>, or neither green label for <a href="#linked-data">Linked Data</a>. The <a href="http://5stardata.info/" target="_blank">5 Open Data diagram</a> is a graphical representation of each of the 5 Star techniques as described by Tim Berners-Lee.
+An easy to read graphic for explaining the 5 Star Linked Data model may be seen on the <a href="http://www.cafepress.com/w3c_shop" target="_blank">5 Star Linked Open Data mug</a>. One reads both green labels for <a href="#linked-open-data">Linked Open Data</a>, or neither green label for <a href="#linked-data">Linked Data</a>. The <a href="http://5stardata.info/" target="_blank">5 Open Data diagram</a> is a graphical representation of each of the 5 Star techniques as described by Tim Berners-Lee.
</section>
<section>
@@ -63,28 +61,18 @@
</section>
<section>
-<h4>Authoritative Open Data</h4>
-Government agencies or authorities are often in a unique position and able to collect data that no other entity can. Open government data is nearly always collected at tax-payers expense and is viewed by the public and government, as valuable if made available with proper context and an open license. Linked Data is seen by many to be a useful approach to publish and consume authoritative open data. Authoritative open data that conforms to <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html" target="_blank">Best Practices for Publishing Linked Data</a> may enjoy a greater chance of being discovered and re-used by others.
-</section>
-
-<section>
-<h4>Creative Commons Licenses</h4>
-Creative Commons copyright licenses and tools aim to forge a balance inside the traditional “all rights reserved” setting that copyright law creates. Creative Commons licenses and tools provide a simple, standardized way to grant copyright permissions to their creative work. The combination of our tools and our users is a vast and growing digital commons, a pool of content that can be copied, distributed, edited, remixed, and built upon, all within the boundaries of copyright law. See also <a href="http://creativecommons.org/licenses/" taget="blank">About Creative Commons Licenses</a>.
-</section>
-
-<section>
<h4>CC-BY-SA License</h4>
-CC-BY-SA is a form of Creative Commons license for resources released online. 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.
+A form of Creative Commons license for resources released online. Work available under a <a href="http://creativecommons.org/licenses/by-sa/3.0/" target="_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>
-Closed world is 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. See also <a href="#open-world">Open World</a>.
</section>
<section >
<h4>Connection</h4>
-Connection is a concept from computer networking. It refers to a transport layer virtual circuit established between two programs for the purpose of communication.
+A concept from computer networking. It refers to a transport layer virtual circuit established between two programs for the purpose of communication.
</section>
<section>
@@ -94,32 +82,37 @@
<section>
<h4>Content Negotiation</h4>
-Content negotiation, often called "conneg", refers to a phase in establishing a network connection. It is a mechanism for selecting the appropriate representation when servicing a request. The representation of entities in any response can be negotiated (including error responses). See also [<a href="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#content.negotiation" target="blank">HTTP Protocol 1.1</a>]. See also <a href="#connection">Connection</a>.
+Also called "conneg", refers to a phase in establishing a network connection. In the HTTP Protocol, the use of a message header to indicate which response formats a client will accept. Content negotiation allows HTTP servers to provide different versions of a resource representation in response to any given URI request. See also [<a href="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#content.negotiation" target="_blank">HTTP Protocol 1.1</a>]. See also <a href="#connection">Connection</a>.
</section>
<section >
<h4>Controlled Vocabulary</h4>
-A controlled vocabulary is a selected set of terms that can be used to index, tag or describe units of information. By providing a restricted and managed set of terms they can be used to reduce ambiguity in information systems. Such vocabularies may be unstructured (e.g. code lists) or may be organized into increasingly complex knowledge organization schemes (<a href="#taxonomy">taxonomies</a>, thesauri, <a href="#ontology">ontologies</a>). In traditional settings the terms in the controlled vocabularies are words or phrases, in a linked data setting then they are normally assigned unique identifiers (URIs) which in turn link to descriptive phrases.
+Carefully selected sets of terms that are used to describe units of information; used to create <a href="#taxonomy">taxonomies</a>, thesauri and <a href="#ontology">ontologies</a>. In traditional settings the terms in the controlled vocabularies are words or phrases, in a linked data setting then they are normally assigned unique identifiers (URIs) which in turn link to descriptive phrases.
</section>
<section>
-<h4>Converter</h4>
-Converter refers to a tool or script that converts data from one form to another, e.g., CSV into <a href="#rdf">RDF</a>. Publishing good quality, useful Linked Data requires expression of resources and how they are related. Linked Data modelers work with subject domain experts to make explicit the relationships between resources before converting a data set to RDF.
+<h4>Comma Separated Values (CSV)</h4>
+A tabular data format in which columns of information are separated by comma characters. CSV files are a non-proprietary format and are considered 3-star data on the 5-star scale.
</section>
<section>
-<h4>CSV</h4>
-A CSV (comma separated value) 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 data on the 5-star scale.
+<h4>Creative Commons Licenses</h4>
+Licenses that include legal statements by the owner of copyright in intellectual property specifically allowing people to use or redistribute the copyrighted work in accordance with conditions specified therein. See also <a href="http://creativecommons.org/licenses/" target="_blank">About Creative Commons Licenses</a>.
</section>
<section>
-<h4>curl</h4>
-A command line client to retrieve any data over a wide variety of protocols, including machine readable RDF.
+<h4>CURIEs</h4>
+Compact URI expressions (CURIEs) are an RDFa approach for shortening URIs.
+</section>
+
+<section>
+<h4>cURL</h4>
+A command line Open Source/Free Software client that can transfer data, including machine readable RDF, from or to a server using one of its many supported protocols.
</section>
<section >
<h4>Data Cloud</h4>
-Data cloud, also called the <a href="http://richard.cyganiak.de/2007/10/lod/" target="_blank">Linked Data Cloud</a>, is a visual representation of datasets published as Linked Data. Using metadata generated by directories, including CKAN, the project records datasets by domain. The Linked Data Cloud has doubled in size every 10 months since 2007 and as of late 2012 consists of more than 300 data sets from various domains, including geography, media, government and life sciences, according the [<a href="http://lod-cloud.net/state/">State of the LOD Cloud</a>], website and visualizations maintained by C. Bizer, A. Jentzsch, R. Cyganiak. The original data owners/stewards publish one third of the data contained in the Linked Open Data Cloud, while third parties publish 67%. Many academic institutions republish data from their respective governments as <a href="#linked-data">Linked Data</a>, often enhancing the representation in the process.
+Data cloud, also called the <a href="http://richard.cyganiak.de/2007/10/lod/" target="_blank">Linked Data Cloud</a>, is a visual representation of datasets published as Linked Data. Many academic institutions republish data from their respective governments as <a href="#linked-data">Linked Data</a>, often enhancing the representation in the process.
</section >
<section >
@@ -134,22 +127,27 @@
<section>
<h4>Data Modeling</h4>
-Data modeling is a process used to define and analyze data requirements for an information system. In the context of Linked Data Modeling, it is a process that involves professional data modelers working closely with business stakeholders to define and document implicit and explicit relationships. Linked Data modeling applies formal Linked Data modeling techniques based on <a href="#linked-data-principles">Linked Data Principles</a>.
+Data modeling is a process of organizing data and information describing it into a faithful representation of a specific domain of knowledge. Linked data modeling applies modeling techniques based on <a href="#linked-data-principles">Linked Data Principles</a>.
+</section>
+
+<section>
+<h4>Dataset, RDF</h4>
+A collection of RDF data, comprising one or more RDF graphs that is published, maintained, or aggregated by a single provider. In SPARQL, an RDF Dataset represents a collection of RDF graphs over which a query may be performed.
</section>
<section>
<h4>Data Warehouse</h4>
-A data warehouse is one approach to data integration in which data from various operational data systems is extracted, cleaned, transformed and copied to a centralized repository. The centralized repository can then be used for data mining or answering analytical queries. By contrast, Linked Data <em>assumes and accounts</em> for a <em>distributed approach</em> using HTTP URIs to describe and access information resources. A Linked Data approach is seen as an valid alternative to the centralized data warehouse approach especially when integrating open government datasets.
+A data warehouse is one approach to data integration in which data from various operational data systems is extracted, cleaned, transformed and copied to a centralized repository. The centralized repository can then be used for data mining or answering analytical queries. By contrast, Linked Data assumes a <em>distributed approach </em>of data management using HTTP URIs to describe and access information resources. A Linked Data approach is seen as an valid alternative to the centralized data warehouse approach especially when integrating datasets available on the public Web.
</section>
<section >
<h4>DBpedia</h4>
-DBpedia is a community effort to extract structured information from Wikipedia and make it available on the Web. DBpedia is often depicted as a hub for the <a href="#data-cloud">Data Cloud</a>. An RDF representation of the metadata derived from Wikipedia is made available for SPARQL queries and linking to other datasets on the Web. DBpedia also provides a human readable version of the structured content. For example, the human readable version of Linked Data for the color "Red" is found on DBpedia at <a href="http://dbpedia.org/page/Red">http://dbpedia.org/page/Red</a>. See also [<a href="#curl">curl</a>].
+DBpedia is a community effort to extract structured information from Wikipedia and make it available on the Web. DBpedia is often depicted as a hub for the <a href="#data-cloud">Data Cloud</a>. An RDF representation of the metadata held in Wikipedia and made available for SPARQL query on the World Wide Web.
</section >
<section>
<h4>Dereferenceable URIs</h4>
-When an HTTP client can look up a <a href="#uri">URI</a> using the HTTP protocol and retrieve a description of the resource, it is called a dereferenceable URI. Per Linked Data Principles, we identify things using HTTP URIs and provide information about them when an HTTP URI is resolved or dereferenced. Dereferenceable URIs applies to URIs that are used to identify classic HTML documents and URIs that are used in the Linked Data context [[COOL-SWURIS]] to identify real-world objects and abstract concepts.
+When an HTTP client can look up a <a href="#uri">URI</a> using the HTTP protocol and retrieve a description of the resource, it is called a dereferenceable URI. Dereferenceable URIs applies to URIs that are used to identify classic HTML documents and URIs that are used in the Linked Data context [[COOL-SWURIS]] to identify real-world objects and abstract concepts.
</section>
<section>
@@ -164,7 +162,7 @@
<section>
<h4>DCMI</h4>
-See <a href="#dublin-core-metadata-initiative">Dublin Core Metadata Initiative</a>
+See <a href="#dublin-core-metadata-initiative" target="_blank">Dublin Core Metadata Initiative</a>
</section>
<section>
@@ -179,27 +177,42 @@
<section>
<h4>Domain Name System (DNS)</h4>
-Domain Name System (DNS) refers to the Internet's mechanism for mapping between a human-readable host name (e.g. <a href="http://www.example.com">www.example.com</a>) and an Internet Protocol (IP) Address (e.g. 203.20.51.10).
+Domain Name System (DNS) refers to the Internet's mechanism for mapping between a human-readable host name (e.g. <a href="http://www.example.com" target="_blank">www.example.com</a>) and an Internet Protocol (IP) Address (e.g. 203.20.51.10).
</section>
<section>
<h4>Dublin Core Metadata Element Set</h4>
-Dublin Core Metadata Element Set refers to a <a href="#vocabulary">vocabulary</a> of fifteen properties for use in resource descriptions, such as may be found in a library card catalog (creator, publisher, etc). The Dublin Core Metadata Element Set, also known as "DC Elements", is the most commonly used vocabulary for Linked Data applications. See also <a href="http://dublincore.org/documents/dces/"> Dublin Core Element Set, Version 1.1 Specification.</a> [<a href="#dublin-core-metadata-initiative" target="_blank">DCMI</a>]
+Dublin Core Metadata Element Set refers to a <a href="#vocabulary">vocabulary</a> of fifteen properties for use in resource descriptions, such as may be found in a library card catalog (creator, publisher, etc). The Dublin Core Metadata Element Set, also known as "DC Elements", is the most commonly used vocabulary for Linked Data applications. See also <a href="http://dublincore.org/documents/dces/" target="_blank"> Dublin Core Element Set, Version 1.1 Specification.</a> [<a href="#dublin-core-metadata-initiative" target="_blank">DCMI</a>]
</section>
<section>
<h4>Dublin Core Metadata Initiative</h4>
-<a href="http://dublincore.org/about-us/" target="_blank">The Dublin Core Metadata Initiative (DCMI)</a> is an open international organization engaged in the development of interoperable metadata standards, including the Dublin Core Element Set. The DCMI manages long term curation and development of DCMI <a href="http://dublincore.org/specifications/" target="_blank"> specifications and metadata terms namespaces</a>
+A public, not-for-profit organization with a mission to promote interoperable metadata design and innovative practice. <a href="http://dublincore.org/about-us/" target="_blank">The Dublin Core Metadata Initiative (DCMI)</a> manages the long-term curation and development of metadata standards such as the Dublin Core Element Set and DCMI Metadata Terms.
+</section>
+
+<section>
+<h4>Dublin Core Metadata Terms</h4>
+A vocabulary of bibliographic terms used to describe both physical publications and those on the Web. An extended set of terms beyond those basic terms found in the Dublin Core Metadata Element Set. See also <a href="http://dublincore.org/documents/dcmi-terms/" target="_blank">Dublin Core Metadata Terms</a>
</section>
<section>
<h4>Entity</h4>
-The term entity refers to anything that can be named using an HTTP URL. It serves as the <a href="#subject">Subject</a> of a description.
+In the sense of an entity-attribute-value model, an entity is synonymous with the <a href="#subject">Subject</a> of an RDF Triple.
</section>
<section>
<h4>ETL</h4>
-ETL is an abbreviation for extact, transform, load. Linked Data modelers and developers extract data from a relational database, transform to a Linked Data serialization, and then load it into an RDF database.
+ETL is an abbreviation for extract, transform, load. Linked Data developers routinely extract data from a relational database, transform data to RDF Triples, and load it into an RDF database.
+</section>
+
+<section>
+<h4>FOAF</h4>
+See Friend of a Friend.
+</section>
+
+<section>
+<h4>Fragment Identifier</h4>
+The part of an HTTP URI that follows a hash symbol (‘#’). Fragment identifiers are not passed to Web servers by Web clients such as Web browsers.
</section>
<section>
@@ -208,13 +221,23 @@
</section>
<section>
-<h4>Graph</h4>
-Graph refers to a mathematical structure consisting of a collection of objects, represented by "nodes", and connected by “edges” (also called links), to denote inter-relationships between them. It is well established as the field of Graph Theory. See also <a href="#directed-graph">Directed Graph</a>.
+<h4>Friend of a Friend</h4>
+A Semantic Web vocabulary describing people and their relationships for use in resource descriptions. Commonly called "FOAF".
</section>
<section>
-<h4>HyperText Markup Language (HTML)</h4>
-HyperText Markup Language (HTML) is the predominant markup language for hypertext pages on the Web. HTML defines the structure of Web pages and it is a family of W3C standards.
+<h4>Government Open Data</h4>
+Many government authorities have mandated publication of data to the public Web. The broad intention is to facilitate the maintenance of open societies and support governmental accountability and transparency initiatives. To realize the goals of improved efficiency, transparency and accountability, re-use of structured content available on the Web is enhanced by following <a href="#linked-data-principles">Linked Data Principles</a>.
+</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="#directed-graph">Directed Graph</a>.
+</section>
+
+<section>
+<h4>HyperText Markup Language</h4>
+The predominant markup language for hypertext pages on the Web. HyperText Markup Language (HTML) defines the structure of Web pages and is a family of W3C standards.
</section>
<section>
@@ -223,18 +246,8 @@
</section>
<section>
-</h4>HTTP URIs</h4>
-See <a href="uniform-resource-identifiers">Uniform Resource Identifiers (URI)</a>.
-</section>
-
-<section>
-<h4>International Standards Organization (ISO)</h4>
-International Standards Organization (ISO) is 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 (IETF)</h4>
- Internet Engineering Task Force (IETF) is an open international community concerned with the evolution of Internet architecture and the operation of the Internet. It has defined standards such as HTTP and DNS.
+<h4>HTTP URIs</h4>
+See <a href="uniform-resource-identifier">Uniform Resource Identifier</a>.
</section>
<section>
@@ -243,96 +256,110 @@
</section>
<section>
+<h4>International Organization for Standards (ISO)</h4>
+ISO refers to a network of the national standards institutes of over 160 countries that cooperate to define international standards. It defines many standards including, in the linked data context, formats for dates and currency. See also <a href="http://www.iso.org/iso/home.html" target="_blank">[ISO website]</a>.
+</section>
+
+<section>
+<h4>Internet Engineering Task Force (IETF)</h4>
+IETF is an open international community concerned with the evolution of Internet architecture and the operation of the Internet. It has defined standards such as HTTP and DNS.
+</section>
+
+<section>
+<h4>Internationalized Resource Identifier</h4>
+A global identifier standardized by joint action of the World Wide Web Consortium and Internet Engineering Task Force. An IRI may or may not be resolvable on the Web. A generalization of URIs that allow characters from the Universal Character Set (Unicode). Slowly replacing URIs. See also <a href="#uniform-resource-identifier">Uniform Resource Identifier (URI)</a>, <a href="#uniform-resource-locator">Uniform Resource Locator (URL)</a>. Also called IRI.
+</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. See [[!RFC4627]] for details.
</section>
<section>
<h4>JSON-LD</h4>
-JSON-LD (JavaScript Object Notation for Linking Data) [[JSON-LD]] 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>
-<a href="http://jena.apache.org">Jena</a> is an Open Source Software implementation of a <a href="#semantic-web">Semantic Web</a> development framework. It supports the storage, retrieval and analysis of <a href="#rdf">RDF</a> information.
+JavaScript Object Notation for Linking Data (JSON-LD) [[JSON-LD]] is a language-independent data format for representing Linked Data, based on JSON. JSON-LD is capable of serializing any RDF graph or dataset and most, but not all, JSON-LD documents can be directly transformed to RDF. <a href="http://json-ld.org/spec/FCGS/json-ld-syntax/20120626/" target="_blank"> 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 an appropriate Linked Data interchange language for JavaScript environments, Web service and NoSQL databases.
</section>
<section>
<h4>Linked Data</h4>
-Linked data refers to a set of best practices for creating, publishing and announcing structured data on the Web. See [<a href="#linked-data-principles">Linked Data Principles</a>] Linked Data is intended for access by both humans and machines. Linked Data is not the same as <a href="rdf">RDF</a>, rather Linked Data uses the RDF family of standards for data interchange ( RDF/XML, RDFa, Turtle) and query (SPARQL). 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><a href="#linked-open-data">Linked Open Data</a></em>.
+A pattern for hyperlinking machine-readable data sets to each other using Semantic Web techniques, especially via the use of RDF and URIs. Enables distributed SPARQL queries of the data sets and a browsing or discovery approach to finding information (as compared to a search strategy). Linked Data is intended for access by both humans and machines. Linked Data uses the RDF family of standards for data interchange (e.g., RDF/XML, RDFa, Turtle) and query (SPARQL). If Linked Data is published on the public Web, it is generally called <em><a href="#linked-open-data">Linked Open Data</a></em>. See also [<a href="#linked-data-principles">Linked Data Principles</a>].
</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" target="_blank"> gFacet</a>, and the <a href="http://callimachusproject.org" target="_blank">Callimachus Shell (CaSH)</a>.
+<h4>Linked Data API</h4>
+A REST API that allows data publishers to provide URLs to lists of things and clients to retrieve machine-readable data from those URLs.
</section>
<section>
-<h4>Linked Data Platform 1.0</h4>
-A set of best practices and simple approach for a read-write Linked Data architecture, based on HTTP access to web resources that describe their state using the RDF data model. The Linked Data Platform describes the use of HTTP for accessing, updating, creating and deleting resources from servers that expose their resources as Linked Data. It provides some new rules as well as clarifications and extensions of the four rules of Linked Data [[LINKED-DATA]]. See also [[LDP-ONE]]
+<h4>Linked Data client</h4>
+A Web client that supports HTTP content negotiation for the retrieval of Linked Data from URLs and/or SPARQL endpoints. A Linked Data client understands standard REST API, for example the Linked Data REST API. Examples of Linked Data clients include: Tim Berners-Lee's early <a href="http://www.w3.org/2005/ajar/tab.html" target="_blank"> Tabulator browser</a>, <a href="http://www.visualdataweb.org/gfacet.php" target="_blank"> gFacet</a>, and the <a href="http://callimachusproject.org" target="_blank">Callimachus Shell (CaSH)</a>.
+</section>
+
+<section>
+<h4>Linked Data Platform</h4>
+A specification that defines a REST API to read and write Linked Data for the purposes of enterprise application integration. The Linked Data Platform describes the use of a REST API for accessing, updating, creating and deleting resources from servers. See also [[LDP-ONE]]
</section>
<section>
<h4>Linked Data Principles</h4>
-Tim Berners-Lee, the inventor of the Web and initiator of the <a href="http://www.w3.org/DesignIssues/LinkedData.html" target="_blank"> Linked Data</a> project, proposed the following principles upon which Linked Data is based:
+Provide a common <a href="#api">API</a> for data on the Web which is more convenient than many separately and differently designed APIs published by individual data suppliers. Tim Berners-Lee, the inventor of the Web and initiator of the <a href="http://www.w3.org/DesignIssues/LinkedData.html" target="_blank"> Linked Data</a> project, proposed the following principles upon which Linked Data is based:
<ol>
<li>Use URIs to name things;</li>
<li>Use HTTP URIs so that things can be referred to and looked up ("dereferenced") by people and user agents;</li>
<li>When someone looks up a URI, provide useful information, using the open Web standards such as RDF, SPARQL;</li>
<li>Include links to other related things using their URIs when publishing on the Web.</li>
</ol>
-Linked Data Principles provide a common <a href="#api">API</a> for data on the Web which is more convenient than many separately and differently designed APIs published by individual data suppliers.
</section>
<section>
<h4>Linked Open Data</h4>
-Linked Open Data refers to Linked Data published on the <em>public Web</em>, often abbreviated as "LOD". Publishing Linked Open Data enables distributed <a href="#sparql">SPARQL</a> queries of the data sets and a "browsing" or "discovery" approach to finding information, as compared to a search strategy. See also: [[LD-FOR-DEVELOPERS]], [[HOWTO-LODP]]
+Linked Data published on the public Web and licensed under one of several open content licenses permitting reuse.
+Publishing Linked Open Data enables distributed <a href="#sparql">SPARQL</a> queries of the data sets and a "browsing" or "discovery" approach to finding information, as compared to a search strategy. See also: [[LD-FOR-DEVELOPERS]], [[HOWTO-LODP]]
</section>
<section>
<h4>Linked Open Data Cloud</h4>
-The Linked Data Cloud represents interconnected datasets that have been published as Linked Data on the public Web. See also: <a href="#data-cloud">Data Cloud</a>, <a href="#linked-open-data-cloud-diagram">Linked Open Data Cloud diagram</a>
+A colloquial phrase for the total collection of Linked Data published on the Web. See also: <a href="#data-cloud">Data Cloud</a>, <a href="#linked-open-data-cloud-diagram">Linked Open Data Cloud diagram</a>
</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.
-</section>
-
-<section>
-<h4>Linking Government Data</h4>
-Linking government data refers to the use of tools and techniques of the Semantic Web to connect, expose and use data from government systems.
+A diagram representing datasets published by the Linking Open Data project from 2007-2011. The diagram stopped being updated when individual datasets could no longer be meaningfully represented in a single diagram due to the number of total datasets. See the pictoral depiction of the <a href=" http://lod-cloud.net/" target="blank">Linked Data Cloud</a>.
</section>
<section>
<h4>Linking Open Data Project</h4>
-The Linking Open Data project is a community activity started in 2007 by the W3C's <a href="http://www.w3.org/wiki/SweoIG/TaskForces/CommunityProjects/LinkingOpenData" target="_blank">Semantic Web Education and Outreach (SWEO) Interest Group</a>. The project's stated goal is to "make data freely available to everyone".
+A community activity started in 2007 by the W3C's <a href="http://www.w3.org/wiki/SweoIG/TaskForces/CommunityProjects/LinkingOpenData" target="_blank">Semantic Web Education and Outreach (SWEO) Interest Group</a>. The project's stated goal is to "make data freely available to everyone".
</section>
<section>
-<h4>Machine Readable Data</h4>
-<p>Machine readable gets 2-stars on the <a href="#5-star-linked-data">5-star Linked Data scale</a>. While some open data developers use screen-scrapping techniques to parse machine readable content, using 4-star or 5-star Linked Data is preferable in terms of provenance and ease of reuse. Anything less than 4-star data gives Web developers more work modeling and transforming data. By creating and publishing Linked Data, you are increasing the ability of search engines, and thus humans, to find, access and re-use information.
+<h4>Linkset</h4>
+A collection of RDF links between two datasets.
+</section>
+
+<section>
+<h4>Machine Readable Data</h4>
+<p>Data formats that may be readily parsed by computer programs without access to proprietary libraries. For example, CSV, TSV and RDF formats are machine readable, but PDF and Microsoft Excel are not. Creating and publishing data following Linked Data principles helps search engines and humans to find, access and re-use data. Once information is found, computer programs can re-use data without the need for custom scripts to manipulate the content.
</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">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>
-Thus, you've seen how the same data can be viewed in human and machine readable format from the same page.
+Publishing machine readable data using Linked Data principles provides a human and machine readable version. For example, Wikipedia includes a Web page about the color <a href="http://wikipedia.org/wiki/Red" target="_blank">Red</a>. DBpedia, the database containing structured content contained in Wikipedia, allows a Linked Data client to look up "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>
</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.
+The basic unit of HTTP communication. It consists 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>
-Metadata literally means data about data. It refers to the information used to administer, describe, preserve, present, use or link other information held in resources, especially knowledge resources, be they physical or virtual.
+Information used to administer, describe, preserve, present, use or link other information held in resources, especially knowledge resources, be they physical or virtual. Metadata may be further subcategorized into several types (including general, access and structural metadata). Linked Data incorporates human and machine readable metadata along with it, making it self describing.
</section>
<section>
<h4>Metadata Object Description Schema</h4>
-It is a bibliographic description system intended to be a compromise between <a href="http://www.loc.gov/marc">MARC</a> and <a href="http://dublincore.org/">DC metadata</a>. It is implemented in <a href="#xml-schema">XML Schema</a>. See DC, MARC, XSD.
+It is a bibliographic description system intended to be a compromise between <a href="http://www.loc.gov/marc" target="_blank">MARC</a> and <a href="http://dublincore.org/" target="_blank">DC metadata</a>. It is implemented in <a href="#xml-schema">XML Schema</a>. See DC, MARC, XSD.
</section>
<section>
@@ -346,40 +373,43 @@
</section>
<section>
-<h4>Namespace</h4>
-Namespace refers to a container for a set of names that belong to a single authority. Namespaces allow different agents to use the same word in different ways.
+<h4>Namespace IRI</h4>
+A namespace IRI is a base IRI shared by all terms in a given vocabulary or ontology.
+</section>
+
+<section>
+<h4>Natural Keys</h4>
+Human-readable categories and sub-identifiers within a URI that reflect what the identifier describes. They are recommended when creating URIs so that people reading RDF in its source format (mostly developers) will be able to more quickly understand it.
+</section>
+
+<section>
+<h4>Neutral URI</h4>
+A URI that avoids the exposure of implementation details within the URI itself.
+</section>
+
+<section>
+<h4>N-Triples</h4>
+A subset of Turtle that defines a line-based format to encode a single RDF graph. Used primarily as an exchange format for RDF data. See also <a href="http://www.w3.org/TR/n-triples/">N-triples</a>
</section>
<section>
<h4>Object</h4>
-In the context of <a href="#rdf">RDF</a>, the object is the third part of an RDF statement. It is the property value that is mapped to a subject by the predicate. See also [<a href="#subject">Subject</a>] [<a href="#predicate">Predicate</a>]
+In the context of <a href="#rdf">RDF</a>, the object is the final part of an RDF statement. See also [<a href="#subject">Subject</a>] [<a href="#predicate">Predicate</a>]
</section>
<section>
<h4 >Ontology</h4>
-An ontology is a formal model of a domain. It describes the types of things that exist (classes), the relationships between them (properties) and the logical ways those classes and properties can be used together (axioms). The OWL (Web Ontology Language) family of languages provide a standardized-means for expressing and exchanging ontologies. It builds upon, and is compatible with, <a href="#rdf">RDF</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, reconciliation, query answering, data translation, or for navigation on the semantic web.
+A formal model that allows knowledge to be represented for a specific domain. An ontology describes the types of things that exist (classes), the relationships between them (properties) and the logical ways those classes and properties can be used together (axioms).
</section>
<section>
<h4>Open Government Data</h4>
-Open government data broadly refers to content that is published on the public Web by government authorities at national, regional or local levels, in a variety of non-proprietary formats including as XML, CSV, SHP and PDF.
-</section>
-
-<section>
-<h4>Open World</h4>
- Open world is a concept from Artificial Intelligence (AI) and refers to a model of uncertainty that an agent assumes about the external world. In an open world, the agent presumes that what is not known to be true may yet be true if additional information is later obtained. It is the assumption underlying RDF and OWL Full, and often opposed to <a href="#closed-world">"Closed World".</a>
+Refers to content that is published on the public Web by government authorities in a variety of non-proprietary formats.
</section>
<section>
<h4>ORG Ontology</h4>
-ORG is an RDF vocabulary to enable publication of information about organizations and organizational structures, even at governmental level. See also [<a href="http://www.w3.org/TR/vocab-org/">http://www.w3.org/TR/vocab-org/</a>]
+ORG is an RDF vocabulary to enable publication of information about organizations and organizational structures, even at governmental level. See also [<a href="http://www.w3.org/TR/vocab-org/" target="_blank">http://www.w3.org/TR/vocab-org/</a>]
</section>
<section>
@@ -389,27 +419,22 @@
<section>
<h4>Persistent Uniform Resource Locator</h4>
-A persistent uniform resource locator (PURL) is a <a href="uniform-resource=locator">uniform resource locator</a> (URL) that is intended to remain the same over the course of time, regardless of changes to the implementing technology, the ownership of the resource or the contents of the representation. There are several types of PURLs, which are differentiated by the HTTP status code they return. PURLs are used to curate the URL resolution process, thus solving the problem of transitory URIs in location-based URI schemes like HTTP. Thus, a user of a PURL always uses the same Web address, even though the resource in question may have moved or changed ownership. A PURL might redirect to the new location or return content proxied from the new location.
+URLs that act as permanent identifiers in the face of a dynamic and changing Web infrastructure. Persistent Uniform Resource Locators (PURLs) redirect to the current location of or proxy specific Web content. A user of a PURL always uses the same Web address, even though the resource in question may have moved or changed ownership.
</section>
<section>
<h4>Predicate</h4>
-The predicate is the second part of an <a href="#rdf">RDF</a> statement and gives the property which connects the subject of the statement to the object of the statement. Thus in the informal statement <em>"Alice knows Bob"</em> then <em>"knows"</em> is the predicate which connects "Alice" (the subject of the statement) to "Bob" (the object of the statement). The term predicate derives from predicate calculus. In RDF we use the terms predicate (for the role) and property (for the thing that plays that role) regardless of whether the value of the property is a simple literal or some other resource.
+The middle term (the linkage, or "verb") in an RDF statement. For example, in the statement <em>"Alice knows Bob"</em> then <em>"knows"</em> is the predicate which connects "Alice" (the subject of the statement) to "Bob" (the object of the statement).
+</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. One of the most common Internet protocols is the Hypertext Transfer Protocol (HTTP).
</section>
<section>
<h4>Provenance</h4>
-Provenance refers to the sources of information, such as entities and processes, involved in producing or delivering an artifact. An ontology expressing the provenance data model in OWL2 [[!PROV-O]] is used to represent and interchange provenance information generated in different systems and under different contexts.
-</section>
-
-<section>
-<h4>Protocol</h4>
-Protocol, in the context of computing, refers to 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>
-Public Sector Information, also called public information, is the information created by a government in the course of governing. In most democracies, such information can be made available to people in due course of time.
+Data related to where, when and how information was acquired.
</section>
<section>
@@ -419,22 +444,22 @@
<section>
<h4>Quad Store</h4>
-Quad Store is a colloquial phrase for an RDF database that stores RDF triples plus an additional element of information, often used to collect statements into groups. This notion has been clarified and standardized in <a href="#sparql">SPARQL</a> in the form of <b>RDF Datasets</b>
+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 <a href="#linked-data">Linked Data</a> implies programmatic retrieval of resources and their relationships from the Web of Data. Using the SPARQL language, developers issue queries based on (triple) patterns. <a href="#sparql">SPARQL</a> 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.
+Programmatic retrieval of resources and their relationships. Using the SPARQL language, developers issue queries based on (triple) patterns.
</section>
<section>
<h4>R2RML</h4>
-<a href="http://www.w3.org/TR/r2rml/">R2RML</a> (RDB to RDF Mapping Language) is a language for expressing customized mappings from relational databases to RDF datasets. Such mappings provide the ability to view existing relational data in the RDF data model, expressed in a structure and target vocabulary of the mapping author's choice.
+<a href="http://www.w3.org/TR/r2rml/" target="_blank">R2RML</a> (RDB to RDF Mapping Language) is a language for expressing customized mappings from relational databases to RDF datasets. Such mappings provide the ability to view existing relational data in the RDF data model, expressed in a structure and target vocabulary of the mapping author's choice.
</section>
<section>
<h4>Raw Data</h4>
-Raw data refers to machine-readable files from the 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.
+Raw data refers to machine-readable files from the wilderness released without any specific effort to make them applicable to a particular application. Raw data typically requires additional scripts or programs to process the data.
</section>
<section>
@@ -448,69 +473,73 @@
</section>
<section>
-<h4>Resource</h4>
-A resource is anything that can be addressed by a <a href="#uniform-resource-identifiers">Unified Resource Identifier (URI)</a>.
-</section>
-
-<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>
+<h4>RDF database</h4>
+A type of database designed specifically to store and retrieve RDF information. May be implemented as a triple store, quad store or other type.
</section>
<section>
-<h4>Resource Description Framework in Attributes</h4>
-Resource Description Framework in Attributes (RDFa) is a key enabling technology to add structured data to HTML pages directly. RDFa is a technique that provides a set of markup attributes to augment the visual information on the Web with machine-readable hints. [[!RDFa-PRIMER]]</section>
-
-<section>
-<h4>RDF Database</h4>
- A type of database designed specifically to store and retrieve RDF information.
-</section>
-
-<section>
-
<h4>RDF-JSON</h4>
-<p class='todo'>In favor of removing this item: DaveR. In favor of keeping: Bhyland. To discuss</p>
-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. See also [<a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-json/index.html"> RDF 1.1 JSON Serialization document draft</a>]
+A name for one of the early proposals for how to serialized RDF in JSON. RDF-JSON is still widely used. Originally proposed as a <a href="http://docs.api.talis.com/platform-api/output-types/rdf-json" target="_blank">Talis Platform API Output Type</a>. See also a concrete syntax in JavaScript Object Notation (JSON) [[!RFC4627]] for RDF as defined in the RDF Concepts and Abstract Syntax [[!RDF-CONCEPTS]] W3C Recommendation and <a href="#json-ld">JSON-LD</a> which are more recent W3C documents.
</section>
<section>
<h4>RDF Schema</h4>
-RDF Schema (RDFS) [[!RDFS]] is the vocabulary 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).
+The simplest RDF vocabulary description language. It provides much less descriptive capability than the Simple Knowledge Organization System (SKOS) or the Web Ontology Language (OWL). A standard of the W3C [[!RDFS]]
+</section>
+
+<section>
+<h4>RDF/XML</h4>
+An RDF syntax encoded in XML. A standard of the W3C. [[!RDFXML]
+</section>
+
+<section>
+<h4>Representational State Transfer (REST)</h4>
+An architectural style for information systems used on the Web. It explains some of the Web's key features, such as extreme scalability and robustness to change. REST is the foundation of the World Wide Web and the dominant Web service design model.
</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 also <a href="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#request" target="blank">RFC 2616bis</a> for an HTTP Request.
+Request refers to a stage in the HTTP protocol. 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.
</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>.
+In an RDF context, a resource can be anything that an RDF graph describes. A resource can be addressed by a <a href="#uniform-resource-identifier">Unified Resource Identifier (URI)</a>.
+</section>
+
+<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>
+</section>
+
+<section>
+<h4>Resource Description Framework in attributes (RDFa)</h4>
+An RDF syntax encoded in HTML documents. RDFa provides a set of markup attributes to augment the visual information on the Web with machine-readable hints. It is a standard of the World Wide Web Consortium. [[!RDFa-PRIMER]]
</section>
<section>
<h4>Response</h4>
-After receiving and interpreting a request message, a server responds with an HTTP response message. See details from [[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.
+An action by a server taken as the result of a request by a client. In HTTP, a response provides a resource representation to the calling client. 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>
<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.
+See <a href="#representational-state-transfer">Representational State Transfer</a>
</section>
<section>
<h4>REST API</h4>
-An application program interface based on Representational State Transfer (REST).
+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>.
</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.
+Schema refers to 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.
+The broad set of technologies that related to the extraction, representation, storage, retrieval and analysis of machine-readable information.
</section>
<section>
@@ -519,58 +548,49 @@
</section>
<section>
-<h4>Semantic Web Stack </h4>
-The Semantic Web Stack is a layered representation of the architecture of the semantic web, constituting of standardized languages and technologies.
+<h4>Semantic Web Search Engine</h4>
+A search engine capable of making use of semantic technologies to model its knowledge base and to deliver content.
</section>
<section>
<h4>Semantic Web Standards</h4>
- Standards of the World Wide Web Consortium (W3C) relating to the Semantic Web, including RDF [[!RDF]], RDFa [[!RDFa-PRIMER]], SKOS [[!SKOS-REFERENCE]], OWL [[!OWL2]] and SPARQL [[!SPARQL]].
-</section>
-
-<section>
-<h4>Semantic Web Search Engine</h4>
-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 (SOA)</h4>
-Service Oriented Architecture (SOA) refers to a set of architectural design guidelines used to expose IT systems as services. The functionality of a service is published to a registry, can be discovered by potential new users, and directly invoked using published standards. A Web Services based system is an example of SOA.
+Standards of the World Wide Web Consortium relating to the Semantic Web, including RDF [[!RDF]], RDFa [[!RDFa-PRIMER]], SKOS [[!SKOS-REFERENCE]], OWL [[!OWL2]] and SPARQL [[!SPARQL]].
</section>
<section>
<h4>Sesame</h4>
-Sesame is an Open Source Software implementation of a Semantic Web development framework. It supports the storage, retrieval and analysis of RDF information. See also [<a href="http://www.openrdf.org">Open RDF</a>].
+Sesame is an Open Source Software implementation of a Semantic Web development framework. It supports the storage, retrieval and analysis of RDF information. See also [<a href="http://www.openrdf.org" target="_blank">Open RDF</a>].
</section>
+
<section>
<h4>Simple Knowledge Organisation System</h4>
Simple Knowledge Organisation System (SKOS) [[!SKOS-REFERENCE]] is a vocabulary description language for RDF designed for representing traditional knowledge organization systems such as enterprise taxonomies in RDF.
</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 RDF [[!SPARQL]]. Just as SQL is used to query relational data, SPARQL is used to query an RDF database. SPARQL 1.1 [[!SPARQL-11]] specification allows more set of operations and queries on a RDF graph content on the Web or in a RDF store.
+<h4>Sindice</h4>
+Sindice is a search engine for Linked Data. It offers search and querying capabilities across the data it knows about, as well as specialized APIs and tools for presenting Linked Data summaries. See also <a href="http://sindice.com" target="_blank">http://sindice.com</a>.
</section>
<section>
-<h4>SPARQL client</h4>
-A SPARQL client is 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.
+<h4>Skolemization</h4>
+Skolemization is a process whereby some RDF databases and other systems implementing the SPARQL query language automatically assign URIs to blank nodes so that they are more easily operated upon.
+</section>
+
+<section>
+<h4>SPARQL</h4>
+SPARQL Protocol and RDF Query Language (SPARQL) defines a query language for RDF data, analogous to the Structured Query Language (SQL) for relational databases. A family of standards of the World Wide Web Consortium. See also <a href="http://www.w3.org/TR/sparql11-overview/" target="_blank">http://www.w3.org/TR/sparql11-overview/</a>.
</section>
<section>
<h4>SPARQL endpoint</h4>
-SPARQL endpoint refers to an application that can answer a SPARQL query, including one where the native encoding of information is not in RDF. It is a best practice for datasets providers to give the URL of their SPARQL endpoint to get access to their data both programmatically or through the web interface. A list of some endpoints status is available at <a href="http://labs.mondeca.com/sparqlEndpointsStatus/">http://labs.mondeca.com/sparqlEndpointsStatus/</a>
-</section>
-
-<section>
-<h4>Structured Query Language (SQL)</h4>
-Structured Query Language (SQL) is a query language standard for relational databases.
+A service that accepts SPARQL queries and returns answers to them as SPARQL result sets. It is a best practice for datasets providers to give the URL of their SPARQL endpoint to allow access to their data programmatically or through a Web interface. A list of some endpoints status is available at <a href="http://labs.mondeca.com/sparqlEndpointsStatus/" target="_blank">http://labs.mondeca.com/sparqlEndpointsStatus/</a>
</section>
<section>
<h4>Subject</h4>
-The subject is the first part of an <a href="#rdf">RDF</a> statement. A subject in the context of a <a href="#triple">triple</a> <?s ?p ?o> refers to who or what the RDF statement is about.
+The subject is the first part of an <a href="#rdf">RDF</a> statement. A subject in the context of a <a href="#triple" target="_blank">triple</a> <?s ?p ?o> refers to who or what the RDF statement is about.
</section>
<section >
@@ -580,41 +600,41 @@
<section >
<h4>Term</h4>
- A term is an entry in a controlled vocabulary, schema, <a href="#taxonomy">Taxonomy</a> or <a href="#ontology">Ontology</a>.
+An entry in a controlled vocabulary, schema, <a href="#taxonomy">Taxonomy</a> or <a href="#ontology">Ontology</a>.
</section >
<section >
<h4>Triple</h4>
- A triple refers to a <a href="#rdf">RDF</a> statement, consisting of two things (a "Subject" and an "Object") and a relationship between them ("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 such statements).
</section >
<section >
<h4>Triple store</h4>
- Triple store is a colloquial phrase for an <a href="#rdf">RDF</a> database that stores RDF triples.
+A colloquial phrase for an <a href="#rdf">RDF</a> database that stores RDF triples.
</section >
<section >
<h4>Tuple</h4>
- Tuple is a mathematical term referring to an ordered list of elements. RDF statements are 3-tuples; an ordered list of three elements.
+RDF statements are 3-tuples; an ordered list of three elements.
</section >
<section >
<h4>Turtle</h4>
-Turtle is 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.
+An RDF serialization format designed to be easier to read than others such as RDF/XML. The term "Turtle" was derived from Terse RDF Triple Language. 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 >
<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">http://dbpedia.org/page/red</a>. URIs can also be used to refer to other data representatations such as a row in a CSV file or a specific table in a relational database.
+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 <a href="http://tools.ietf.org/html/rfc3986" target="_blank">http://tools.ietf.org/html/rfc3986</a> and <a href="http://www.w3.org/DesignIssues/Architecture.html" target="_blank">http://www.w3.org/DesignIssues/Architecture.html</a>.
</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">Web Architecture from 50,000 feet</a>. For definitive information on Uniform Resource Identifiers (URI), see "Uniform Resource Identifier (URI): Generic Syntax," [[!RFC3986]]
+<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]]
</p>
</section >
<section>
<h4>Uniform Resource Locator</h4>
-A Uniform Resource Locator (URL) is a special type of <a href="#uri">URI</a> that resolves on the Web and is commonly called a "Web address." Uniform Resource Locator (URL) is a global identifier for Web resources standardized by joint action of the W3C and IETF. All HTTP URLs are URIs however, not all URIs are URLs.
+A global identifier for Web resources standardized by joint action of the World Wide Web Consortium and Internet Engineering Task Force. A URL is resolvable on the Web and is commonly called a "Web address". All HTTP URLs are URIs however, not all URIs are URLs. See also <a href="#internationalized-resource-identifier">Internationalized Resource Identifier</a> and <a href="#uniform-resource-identifier">Uniform Resource Identifier</a>.
</section>
<section>
@@ -627,45 +647,54 @@
See <a href="#uniform-resource-locator">Uniform Resource Locator</a>
</section>
-
<section>
<h4>Validation Service</h4>
-The W3C offers an RDF validation service to check and validate RDF files. It is considered a best practice to validate RDF files prior to publishing them on the Web. See http://www.w3.org/RDF/Validator/. There are other RDF parsers available, see http://www.w3.org/People/Barstow/#online_parsers.
+The W3C offers an RDF validation service to check and validate RDF files. It is considered a best practice to validate RDF files prior to publishing them on the Web. See <a href="http://www.w3.org/RDF/Validator/" target="_blank">http://www.w3.org/RDF/Validator/</a>. There are other RDF parsers available, see <a href="http://www.w3.org/People/Barstow/" target="_blank">http://www.w3.org/People/Barstow/#online_parsers</a>.
</section>
<section>
<h4>Vocabulary</h4>
-A vocabulary defines the concepts and relationships (also referred to as <a href="#term">"terms"</a>) 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.
+A collection of <a href="#term">"terms"</a> for a particular purpose. Vocabularies can range from simple such as the widely used RDF Schema, FOAF and Dublin Core Metadata Element Set to complex vocabularies 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. The use of this term overlaps with Ontology.
+</section>
+
+<section>
+<h4>Vocabulary Alignment</h4>
+The process of analyzing multiple vocabularies to determine terms that are common across them and to record those relationships.
</section>
<section>
<h4>VoID</h4>
-VoID is an <a href="#rdf-schema">RDF Schema</a> vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. VoID can be used to express general metadata based on Dublin Core, access metadata, structural metadata, and links between datasets. [VOID-GUIDE]
+Vocabulary of Interlinked Datasets, an <a href="#rdf-schema" target="_blank">RDF Schema</a> vocabulary for expressing metadata about RDF datasets and a standard of the World Wide Web Consortium. VoID is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. VoID can be used to express general metadata based on Dublin Core, access metadata, structural metadata, and links between datasets. [VOID-GUIDE]
</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.
+Web 2.0 is 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".
+Web 3.0 is 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. It is considered synonymous with the phrases "Semantic Web" and "The Web of Data".
</section>
<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.
+A subset of the World Wide Web which contains Linked Data.
+</section>
+
+<section>
+<h4>Web of Documents</h4>
+The original, or traditional, World Wide Web in which published resources were nearly always documents.
</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 [[!OWL2]]. Standardized variants include OWL Full, OWL DL (for "description logic") and OWL Lite.
+OWL is a family of knowledge representation and vocabulary description languages for authoring ontologies, based on RDF and standardized by the W3C [[!OWL2]].
</section >
<section>
<h4>World Wide Web Consortium (W3C)</h4>
-<a href="http://www.w3c.org/">World Wide Web Consortium</a>, also known as W3C, is an international community that develops and promote high-quality standards based on consensus around Web technologies. It defined standards such as <a href="http://www.w3.org/standards/webdesign/">Web Design</a>, <a href="http://www.w3.org/standards/webarch/">Web Architecture</a> and <a href="http://www.w3.org/standards/semanticweb/">Semantic Web</a>.
+An international community that develops and promotes protocols and guidelines for the long-term growth for the Web. W3C's standards define key parts of the World Wide Web, including <a href="http://www.w3.org/standards/webdesign/" target="_blank">Web Design</a>, <a href="http://www.w3.org/standards/webarch/" target="_blank">Web Architecture</a> and the <a href="http://www.w3.org/standards/semanticweb/" target="_blank">Semantic Web</a>. See also <a href="http://www.w3.org/Consortium/mission" target="_blank"> W3C Mission</a>.
</section >
<section>
@@ -692,7 +721,7 @@
<!-- ACK -->
<section class="appendix">
<h2>Acknowledgments</h2>
-<p>The editors are grateful to <a href="http://3roundstones.com/about-us/leadership-team/david-wood/">David Wood</a> for the initial glossary terms from the <a href="http://3roundstones.com/linking-government-data/">Linking Government Data</a> book, (<a href="http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-1-4614-1766-8">Springer 2011</a>). The editors would like to thank the members of the <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> who helped to iterate Linked Data Glossary so we have common ground upon which to grow the Web of Data with good quality Linked Data!
+<p>The editors are grateful to <a href="http://3roundstones.com/about-us/leadership-team/david-wood/" target="_blank">David Wood</a> for contributing the initial glossary terms from <a href="http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-1-4614-1766-8" target="_blank">Linking Government Data</a>, (Springer 2011). The editors wish to also thank members of the <a href="http://www.w3.org/2011/gld/" target="_blank">Government Linked Data Working Group</a> with special thanks to the reviewers and contributors: Thomas Baker, Hadley Beeman, Richard Cyganiak, Michael Hausenblas, Benedikt Kaempgen, James McKinney, Marios Meimaris, Jindrich Mynarz, Michael Pendleton and Dave Reynolds who diligently iterated the W3C Linked Data Glossary in order to create a foundation of terms upon which to discuss and better describe the Web of Data. Thank you!
</p>
</section>
</body>