--- a/ReSpec.js/bibref/biblio.js Wed May 25 19:08:23 2011 +0100
+++ b/ReSpec.js/bibref/biblio.js Wed May 25 20:06:29 2011 +0100
@@ -10,6 +10,7 @@
"TAG" : "<a href=\"http://www.w3.org/2001/tag/issues\"><cite>TAG Issues List</cite></a>, W3C Technical Architecture Group. This document is http://www.w3.org/2001/tag/issues",
"RDF-MIME-TYPE" : "<a href=\"http://www.iana.org/assignments/media-types/\"><cite>MIME Media Types</cite></a>, The Internet Assigned Numbers Authority (IANA). This document is http://www.iana.org/assignments/media-types/ . The <a href=\"http://www.w3.org/2001/sw/RDFCore/mediatype-registration\">registration for <code>application/rdf+xml</code></a> is archived at http://www.w3.org/2001/sw/RDFCore/mediatype-registration .",
// New stuff
+ "RDF-PLAINLITERAL" : "Jie Bao; Sandro Hawke; Boris Motik; Peter F. Patel-Schneider; Axel Polleres. <a href=\"http://www.w3.org/TR/2009/REC-rdf-plain-literal-20091027/\"><cite>rdf:PlainLiteral: A Datatype for RDF Plain Literals.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-rdf-plain-literal-20091027/\">http://www.w3.org/TR/2009/REC-rdf-plain-literal-20091027/</a>",
"WELL-KNOWN" : "M. Nottingham; E. Hammer-Lahav. <a href=\"http://tools.ietf.org/html/rfc5785\"><cite>Defining Well-Known Uniform Resource Identifiers (URIs).</cite></a> April 2010. Internet RFC 5785. URL: <a href=\"http://tools.ietf.org/html/rfc5785\">http://tools.ietf.org/html/rfc5785</a>",
"ABC" : "Leo Geurts; Lambert Meertens; Steven Pemberton. <a href=\"http://www.cwi.nl/~steven/abc\"><cite>The ABC Programmer's Handbook.</cite></a> Prentice-Hall. ISBN: 0-13-000027-2. URL: <a href=\"http://www.cwi.nl/~steven/abc\">http://www.cwi.nl/~steven/abc</a>",
--- a/index.html Wed May 25 19:08:23 2011 +0100
+++ b/index.html Wed May 25 20:06:29 2011 +0100
@@ -665,7 +665,7 @@
<p>
-RDF uses URI references to identify resources and properties. Certain
+RDF uses <a title="URI reference">URI references</a> to identify resources and properties. Certain
URI references are given specific meaning by RDF. Specifically, URI
references with the following leading substring are defined by the RDF
specifications:
@@ -781,6 +781,13 @@
<section id="section-XMLLiteral">
<h3>XML Content within an RDF Graph</h3>
+ <p class="issue">The canonicalization rules required for XML literals
+ are quite complicated. Increasingly, RDF is produced and consumed in
+ environments where no XML parser and canonicalization engine is
+ available. A possible change to relax the requirements for the
+ lexical space, while retaining the value space, is under discussion.
+ This is <a href="http://www.w3.org/2011/rdf-wg/track/issues/13">ISSUE-13</a>.</p>
+
<p>RDF provides for XML content as a possible literal value. This
typically originates from the use of
<code>rdf:parseType="Literal"</code> in the RDF/XML Syntax [[!RDF-SYNTAX-GRAMMAR]].</p>
@@ -964,6 +971,13 @@
<section id="section-Graph-URIref">
<h3>RDF URI References</h3>
+ <p class="issue">The definition of <a title="URI reference">URI
+ references</a> anticipated
+ <a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized
+ Resource Identifiers</a> (IRIs) [[!IRI]] and is likely to be
+ replaced with IRIs throughout. This is
+ <a href="http://www.w3.org/2011/rdf-wg/track/issues/8">ISSUE-8</a>.</p>
+
<p>A <dfn title="URI reference">URI reference</dfn> within an RDF graph (an RDF URI reference) is a
Unicode string [[!UNICODE]] that:
</p>
@@ -1040,6 +1054,13 @@
<section id="section-Graph-Literal">
<h3>RDF Literals</h3>
+ <p class="issue">Currently, there are three different
+ kinds of literals for expressing strings: plain literals,
+ <a href=""><code>rdf:PlainLiteral</code></a> [[RDF-PLAINLITERAL]],
+ and <code>xsd:string</code>. Some consolidation of these
+ forms is under consideration. This is
+ <a href="http://www.w3.org/2011/rdf-wg/track/issues/12">ISSUE-12</a>.</p>
+
<p>A <dfn>literal</dfn> in an RDF graph
contains one or two named components.</p>
<p>All literals have a <dfn>lexical form</dfn> being a Unicode
@@ -1200,7 +1221,7 @@
<pre>http://example.com/.well-known/genid/d26a2d0e98334696f4ad70a677abc1f6</pre>
- <p class="note">IETF registration of the <code>genid</code> name is
+ <p class="issue">IETF registration of the <code>genid</code> name is
currently in progress.</p>
<p class="note">RFC 5785 [[WELL-KNOWN]] only specifies well-known URIs,
@@ -1210,12 +1231,55 @@
</section>
+
+<section id="section-multigraph">
+ <h2>Abstract Syntax for Working with Multiple Graphs</h2>
+
+ <div class="issue">
+ <p>The Working Group will standardize a model and semantics for
+ multiple graphs and graphs stores. The
+ <a href="http://www.w3.org/2011/01/rdf-wg-charter">charter</a> notes:</p>
+
+ <blockquote>The RDF Community has used the
+ term “named graphs” for a number of years in various settings,
+ but this term is ambiguous, and often refers to what could rather
+ be referred as quoted graphs, graph literals, URIs for graphs,
+ knowledge bases, graph stores, etc. The term “Support for Multiple
+ Graphs and Graph Stores” is used as a neutral term in this charter;
+ this term is not and should not be considered as definitive.
+ The Working Group will have to define the right term(s).</blockquote>
+
+ <p>Progress on the design for this feature is tracked under multiple
+ issues:</p>
+
+ <ul>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/5">ISSUE-5: Should we define Graph Literal datatypes?</a></li>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/14">ISSUE-14: What is a named graph and what should we call it?</a></li>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/15">ISSUE-15: What is the relationship between the IRI and the triples in a dataset/quad-syntax/etc</a></li>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/17">ISSUE-17: How are RDF datasets to be merged?</a></li>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/22">ISSUE-22: Does multigraph syntax need to support empty graphs?</a></li>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/28">ISSUE-28: Do we need syntactic nesting of graphs (g-texts) as in N3?</a></li>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/29">ISSUE-29: Do we support SPARQL's notion of "default graph"?</a></li>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/30">ISSUE-30: How does SPARQL's notion of RDF dataset relate our notion of multiple graphs?</a></li>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/32">ISSUE-32: Can we identify both g-boxes and g-snaps?</a></li>
+ <li><a href="http://www.w3.org/2011/rdf-wg/track/issues/33">ISSUE-33: Do we provide a way to refer to sub-graphs and/or individual triples?</a></li>
+ </ul>
+ </div>
+</section>
+
</section>
<section id="section-fragID">
<h2>Fragment Identifiers</h2>
+ <p class="issue">This section does not address the case where RDF is
+ embedded in other document formats, such as in RDFa or when an RDF/XML
+ fragment is embedded in SVG. It has been suggested that this may be
+ a general issue for the TAG about the treatment of
+ fragment identifiers when one language is embedded in another. This is
+ <a href="http://www.w3.org/2011/rdf-wg/track/issues/37">ISSUE-37</a>.</p>
+
<p>RDF uses an <a title="URI reference">RDF URI
Reference</a>, which may include a fragment identifier, as a
context free identifier for a resource. RFC 2396 [[!RFC2396]] states that the meaning of a fragment
@@ -1465,6 +1529,7 @@
<h2>Changes from RDF 2004</h2>
<ul>
+ <li>2011-05-25: Added boxes for known WG issues throught the document</li>
<li>2011-05-25: Deleted “Structure of this Document” section, it added no value beyond the TOC</li>
<li>2011-05-25: Implemented resolution of <a href="http://www.w3.org/2011/rdf-wg/track/issues/40">ISSUE-40: Skolemization advice in the RDF dcocument</a> by adding a section on <a href="#section-skolemization">Replacing Blank Nodes with IRIs</a></li>
<li>2011-05-25: rdf:XMLLiteral is disjoint from any datatype not explicitly related to it, per erratum <a href="http://www.w3.org/2001/sw/RDFCore/errata#concept-xmlliteral">[concept-xmlliteral]</a></li>