automerge
authorSandro Hawke <sandro@hawke.org>
Thu, 10 May 2012 07:06:32 -0400
changeset 334 f966d0c0cdb5
parent 333 fd4e135820de
child 335 0968f549a95f
automerge
rdf-spaces/index.html
--- a/rdf-spaces/index.html	Thu May 10 07:06:13 2012 -0400
+++ b/rdf-spaces/index.html	Thu May 10 07:06:32 2012 -0400
@@ -2,7 +2,7 @@
 <html lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-    <title>RDF Spaces</title>
+    <title>RDF Spaces and Datasets</title>
     <style type="text/css">
 .figure { font-weight: bold; text-align: center; }
 table.xsd-types td, table.xsd-types th { border: 1px solid #ddd; padding: 0.1em 0.5em; }
@@ -46,7 +46,7 @@
 
           // if you want to have extra CSS, append them to this list
           // it is recommended that the respec.css stylesheet be kept
-          extraCSS:             ["http://dvcs.w3.org/hg/rdf/raw-file/default/ReSpec.js/css/respec.css"],
+          extraCSS:             ["http://dvcs.w3.org/hg/rdf/raw-file/default/ReSpec.js/css/respec.css", "http://dvcs.w3.org/hg/rdf/raw-file/default/ReSpec.js/css/local.css"],
 
           // editors, add as many as you like
           // only "name" is required
@@ -110,11 +110,43 @@
   semantics for systems which manage multiple collections of RDF data. </p>
 </section>
 
+<section id="sotd">
+  <div class="alert">
+    <h2>Editor's Draft Status</h2>
+    
+    <p>Closing in on FPWD IMHO, but definitely not there yet.</p>
+
+  </div>
+</section>
 
 <section class="informative">
     <h2>Introduction</h2>
 
-    <p>@@@ background, context, and general motivation ... </p>
+
+    <p>The <a href="http://www.w3.org/TR/rdf11-concepts/">Resource
+    Description Framework (RDF)</a> provides a simple declarative way
+    to store and transmit information.  It provides a trivial but
+    effective way to combine information from multiple sources, with
+    graph merging.  This allows information from different people,
+    different organizations, different units within an organization,
+    different servers, different algorithms, etc, to all combined and
+    used together, without any special processing or understanding of
+    the relationships among the providers.</p>
+
+    <p>The basic RDF merge operation may be overly simplistic, though,
+    as extra processing and an understanding of the relationships
+    among the providers may be useful.  This document specifies a way
+    to conveniently handle information coming from multiple sources,
+    by modeling each one as a separate <em>space</em>, and using RDF to
+    express information about these spaces.  In addition to this
+    important concept, we provide a pair of languages&mdash;extensions
+    to exsiting RDF syntaxes&mdash; which can be used to store or
+    transmit in one document the contents of multiple spaces as well
+    as information about them.
+
+    <p>This approach allows for a variety of <a href="#use-cases">use
+    cases</a> to be addressed in a straightforward manner, as shown
+    in <a href="deailed-example" class="sectionRef"></a>.</p>
 
 </section>