--- a/glossary/index.html Thu Feb 28 17:58:57 2013 +0000
+++ b/glossary/index.html Thu Feb 28 18:02:23 2013 +0000
@@ -33,6 +33,11 @@
</section>
<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>
+
+<section>
<h4>Application Programmer Interface(API)</h4>
An API (Application Programming Interface) 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>
@@ -82,6 +87,16 @@
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 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>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.
@@ -97,12 +112,17 @@
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 >
+<section>
<h4>Data Market</h4>
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.
@@ -188,13 +208,18 @@
</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>
JSON has proven to be a highly useful object serialization and messaging format for the Web. In an attempt to harmonize the representation of Linked Data in JSON, a specification outlines a common JSON representation format for expressing directed graphs; mixing both Linked Data and non-Linked Data in a single document is expressed as JSON-LD.
</section>
<section>
<h4>JSON-LD</h4>
-JSON-LD (JavaScript Object Notation for Linking Data) 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 ideal Linked Data interchange language for JavaScript environments, Web service and NoSQL databases.
+JSON-LD (JavaScript Object Notation for Linking Data) 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 ideal Linked Data interchange language for JavaScript environments, Web service and NoSQL databases.
</section>
<section>
@@ -208,6 +233,11 @@
</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>
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>
@@ -215,7 +245,7 @@
<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>
<section>
<h4> Linked Open Data Cloud diagram</h4>
@@ -290,20 +320,25 @@
<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.
+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.
+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>
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>
@@ -403,6 +438,11 @@
</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>
@@ -464,60 +504,65 @@
<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.
+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 >
-<section >
+<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 >
+<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 >
+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 >
+<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 >
+<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".
</section >
-<section >
+<section>
<h4>Web Ontology Language</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 >
+<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 >
+<section>
<h4>eXtensible Hypertext Markup Language</h4>
A family of versions of HTML based on XML and standardized by the W3C.
</section >
-<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 >
+<section>
<h4>XML Schema</h4>
Limitations on the content of an XML document that defines what structural elements are allowed.
</section >
-<
-section >
-<h4>eXtensible Stylesheet Language Transformations</h4>
- Declarative programs to transform one XML document into another XML document.
+
+<section>
+<h4>eXtensible Stylesheet Language Transformations (XSLT)</h4>
+Declarative programs to transform one XML document into another XML document.
</section>