--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/rdf-primer/index.html Wed Dec 05 11:17:05 2012 +0100
@@ -0,0 +1,340 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <title>RDF 1.1 Primer</title>
+ <style>
+.figure { font-weight: bold; text-align: center; }
+ </style>
+ <script src='../ReSpec.js/js/respec.js' class='remove'></script>
+ <script class='remove'>
+ var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "rdf11-primer",
+
+ // if your specification has a subtitle that goes below the main
+ // formal title, define it here
+ // subtitle : "an excellent document",
+
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2009-08-06",
+
+ // if the specification's copyright date is a range of years, specify
+ // the start date here:
+ copyrightStart: "2004",
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+// previousPublishDate: "2004-02-10",
+// previousMaturity: "REC",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-primer/index.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if there is an earler version of this specification at the Recommendation level,
+ // set this to the shortname of that version. This is optional and not usually
+ // necessary.
+ prevRecShortname: "rdf-primer",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Guus Schreiber", url: "http://www.cs.vu.nl/~guus/",
+ company: "VU University Amsterdam", companyURL: "http://www.vu.nl/",
+ },
+ { name: "Yves Raimond", url: "http://moustaki.org/",
+ company: "BBC", companyURL: "http://www.bbc.co.uk",
+ },
+ ],
+ otherContributors: {
+ "Previous editors": [
+ { name: "Frank Manola",
+ },
+ { name: "Eric Miller",
+ },
+ { name: "Brian McBride",
+ },
+ ],
+ },
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ //authors: [
+ // { name: "Your Name", url: "http://example.org/",
+ // company: "Your Company", companyURL: "http://example.com/" },
+ //],
+
+ // name of the WG
+ wg: "RDF Working Group",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/rdf-wg/",
+
+ // name (with the @w3c.org) of the public mailing to which comments are due
+ wgPublicList: "public-rdf-comments",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt
+ // ask your friendly neighbourhood Team Contact.
+ wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46168/status",
+
+ // if this parameter is set to true, ReSpec.js will embed various RDFa attributes
+ // throughout the generated specification. The triples generated use vocabulary items
+ // from the dcterms, foaf, and bibo. The parameter defaults to false.
+ doRDFa: true,
+ };
+
+ </script>
+ </head>
+
+ <body>
+
+<section id="abstract">
+ <p>The Resource Description Framework (RDF) is a language for
+ representing information about resources in the World Wide
+ Web. This primer is designed to provide the reader with the basic
+ knowledge required to effectively use RDF. It introduces the basic
+ concepts of RDF and describes its syntax. It describes how to
+ define RDF vocabularies using the RDF Vocabulary Description
+ Language, and gives an overview of some deployed RDF
+ applications. It also describes the content and purpose of other
+ RDF 1.1 specification documents.</p>
+</section>
+
+
+<section id="section-Introduction">
+ <h2>Introduction</h2>
+
+ <p class="issue">This document reflects current progress of the RDF Working
+ Group towards updating the
+ <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">2004
+ version of the <em>RDF Primer</em></a>. The
+ editors expect to work on a number of issues, some of which are
+ listed in boxes like this throughout the document.</p>
+
+ <p>The Resource Description Framework (RDF) is a framework for
+ describing information about <strong>resources</strong> in the World Wide Web,
+ such as such author and modification time of a
+ Web page or copyright and licensing information of a Web video.</p>
+
+ <p class="note">A Web resource is anything we can point to with a
+ Web identifier. Technically, a Web identifier is called an IRI,
+ short for "International Resource Identifier". A URL (Uniform
+ Resource Locator) which we put in our Web browser is a typical
+ example of an IRI: we can <em>retrieve</em> the resource through
+ the URL. There are also IRIs that are used to identify things we
+ cannot "retrieve", such as people or products. For example, if
+ Bob's home page is <code>http://www.example.com/bob</code> a
+ popular convention is to use the IRI
+ <code>http://www.example.com/bob#me</code> as a Web identifier for
+ Bob. If you insert this IRI in your browser it may or may not
+ retrieve something, but it definitely will not retrieve Bob in
+ person (well, at least not with the current state of the art). </p>
+
+ <p>RDF is intended for situations in which this information needs to
+ be processed by applications, rather than being only displayed to
+ people. RDF provides a common framework for expressing this
+ information so it can be exchanged between applications without
+ loss of meaning. Since it is a common framework, application
+ designers can leverage the availability of common RDF parsers and
+ processing tools. The ability to exchange information between
+ different applications means that the information may be made
+ available to applications other than those for which it was
+ originally created. </p>
+
+ <p>The primer is not a normative document. Normative documentation
+ of RDF can be found in the following documents: </p>
+ <ul>
+ <li>A document describing the basic concepts underlying RDF, as
+ well as abstract syntax ("RDF Concepts and Abstract Syntax" [[!RDF-CONCEPTS]])
+ <li>Specifiations of alternative concrete syntaxes for RDF: Turtle [[TURTLE-TR]], RDFa
+ [[RDFA-PRIMER]], RDF/XML [[RDF-SYNTAX-GRAMMAR]]</li>
+ <li>The RDF Vocabulary Description Language ([[RDF-SCHEMA]]),</li>
+ <li>A document describing the formal model-theoretic semantics
+ of RDF ("RDF Semantics" [[!RDF-MT]])</li>
+ </ul>
+ <p>This primer provides a roadmap for people who want to study the
+ normative RDF documents (see Sec. <a href="#section-roadmap">"Roadmap"</a>. </p>
+
+</section>
+
+<section id="section-data-model">
+
+ <h2>RDF Data Model</h2>
+
+ <section id="subsection-statement">
+
+ <h3>RDF Statement</h3>
+
+ <p>RDF allows us to make statements about resources indetified
+ with an IRI. The format of these statements is simple. It always
+ has the following form:<p>
+ <pre>
+ <subject> <predicate> <object>
+ </pre>
+ <p>The <strong>subject</strong> is the Web resource we like to
+ make a statement about. The <strong>predicate</strong> represents
+ the feature we want to make a statement about. The
+ <strong>object</strong> represents the value of the feature
+ for this subject. Informally speaking, RDF allows us to make
+ statements of the form:</p>
+
+ <pre>
+ <Bob> <is a friend of> <Alice>.
+ <Bob> <is born on> <the 4th of July 1990>.
+ <Leonardo da Vinci> <is the creator of> <the Mona Lisa>.
+ <The Mona Lisa> <is on display in> <the Louvre>.
+ </pre>
+
+ <p>Because RDF statements consist of three elements they are called
+ <strong>triples</strong>. Resources typically occur in multiple
+ triples, for example Bob and the Mona Lisa in the examples above. We
+ can therefore visualise triples as a connected <strong>graph</strong>. Graphs consists
+ of nodes and arcs. The subjects and
+ objects of the triples make up the nodes in the graph; the predicates form the arcs. </p>
+
+ <figure>
+ <img src="images/todo.png" width="50%"
+ alt="Informal graphs of the four sample triples">
+ <figcaption>Informal graphs of the four sample triples</figcaption>
+ </figure>
+
+ <p>Let's look at the three parts in an RDF statement in some more
+ detail.</p>
+
+ <dl>
+ <dt>Subject</dt>
+ <dd>The subject is the thing that the RDF statement is
+ about. The subject is usually a Web identifier, such as a URL. ...</dd>
+
+ <dt>Predicate</dt>
+ <dd>...</dd>
+
+ <dt>Object</dt>
+ <dd>...</dd>
+ </dl>
+
+ <p class="note">Readers familiar with databases could view the RDF
+ data model as a binary database model, where every distinct
+ predicate forms a two-column table with subjects in the first
+ column and objects in the second column. </p>
+
+ <p>In the following sections we discuss the three basic constructs
+ that appear in triples, namely IRIs, literals and blank nodes, in more detail. </p>
+
+ </section>
+
+ <section id="subsection-IRI">
+
+ <h3>IRI</h3>
+
+ <p>
+
+ </section>
+
+ <section id="subsection-literal">
+
+ <h3>Literal</h3>
+
+ <p>
+
+ </section>
+
+ <section id="subsection-blank-node">
+
+ <h3>Blank node</h3>
+
+ <p>
+
+ </section>
+
+</section>
+
+<section id="section-syntax">
+
+ <h2>RDF Syntax</h2>
+
+ <p>RDF has many syntactic forms
+
+ Turtle Syntax
+
+ Namespace prefixes</p>
+
+</section>
+
+<section id="section-vocabulary">
+
+ <h2>RDF Vocabularies</h2>
+
+ <p>
+
+</section>
+
+<section id="section-semantics">
+
+ <h2>RDF Graphs and what you can do with them</h2>
+
+ <p>
+
+</section>
+
+<section id="section=multiple-graphs">
+
+ <h2>Multiple graphs</h2>
+
+</section>
+
+
+<section id="section-roadmap">
+ <h2>Document roadmap</h2>
+</section>
+
+<section id="section-Acknowledgments">
+ <h2>Acknowledgments</h2>
+
+ <p class="issue">This section does not yet list those who made
+ contributions to the RDF 1.1 version, nor does it list the
+ current RDF WG members.</p>
+
+ <p>The RDF 2004 editors acknowledge the contributions from many
+ members of the RDF Core Working Group. Specific thanks are due to
+ Art Barstow, Dave Beckett, Dan Brickley, Ron Daniel, Ben
+ Hammersley, Martyn Horner, Graham Klyne, Sean Palmer, Patrick
+ Stickler, Aaron Swartz, Ralph Swick, and Garret Wilson who,
+ together with the many people who commented on earlier versions of
+ the Primer, provided valuable contributions to this document.
+ In addition, this document contains a significant contribution from
+ Pat Hayes, Sergey Melnik, and Patrick Stickler, who led the
+ development of the RDF datatype facilities described in the RDF
+ family of specifications. </p>
+
+</section>
+
+
+<section class="appendix informative" id="changes">
+ <h2>Changes from RDF 2004</h2>
+
+ <ul>
+ <li>..</li>
+ </ul>
+</section>
+
+
+<section id="references"></section>
+
+ </body>
+</html>
\ No newline at end of file