--- a/ReSpec.js/bibref/biblio.js	Wed Jul 06 09:41:19 2011 -0700
+++ b/ReSpec.js/bibref/biblio.js	Wed Jul 06 09:59:18 2011 -0700
@@ -7,6 +7,10 @@
 // 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>",
+// For Turtle
+   "UNISEC" : "Mark Davis; Michel Suignard. <a href=\"http://www.unicode.org/reports/tr36/\"><cite>Unicode Security Considerations</cite></a> 4 August 2010. URL: <a href=\"http://www.unicode.org/reports/tr36/\">http://www.unicode.org/reports/tr36/</a>",
+   "EBNF-NOTATION" : "Tim Bray; Jean Paoli; C. M. Sperberg-McQueen; Eve Maler; François Yergeau. <a href=\"http://www.w3.org/TR/REC-xml/#sec-notation\"><cite>EBNF Notation</cite></a> 26 November 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-xml/#sec-notation\">http://www.w3.org/TR/REC-xml/#sec-notation</a> ",
+   "N-TRIPLES" : "Jan Grant; Dave Beckett. <a href=\"http://www.w3.org/TR/rdf-testcases/#ntriples\"><cite>N-Triples</cite></a> 10 February 2004. W3C Recommendation. URL:  <a href=\"http://www.w3.org/TR/rdf-testcases/#ntriples\">http://www.w3.org/TR/rdf-testcases/#ntriples</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>",
    "ABNF" : "D. Crocker and P. Overell. <a href='http://www.ietf.org/rfc/rfc5234.txt'><cite>Augmented BNF for Syntax Specifications: ABNF.</cite></a> January 2008. Internet RFC 5234. URL: <a href='http://www.ietf.org/rfc/rfc5234.txt'>http://www.ietf.org/rfc/rfc5234.txt</a>",

--- a/rdf-turtle/index.html	Wed Jul 06 09:41:19 2011 -0700
+++ b/rdf-turtle/index.html	Wed Jul 06 09:59:18 2011 -0700
@@ -928,7 +928,7 @@
           <dd><tt>charset</tt> — this parameter is required when transferring non-ASCII data. If present, the value of <tt>charset</tt> is always <tt>UTF-8</tt>.</dd>
 
           <dt>Encoding considerations:</dt>
-          <dd>The syntax of Turtle is expressed over code points in Unicode [[!UNICODE]]. The encoding is always UTF-8 [[!RFC3629]].</dd>
+          <dd>The syntax of Turtle is expressed over code points in Unicode [[!UNICODE]]. The encoding is always UTF-8 [[!UTF-8]].</dd>
           <dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd>
           <dt>Security considerations:</dt>
           <dd>Turtle is a general-purpose assertion language; applications may evaluate given data to infer more assertions or to dereference URIs, invoking the security considerations of the scheme for that URI. Note in particular, the privacy issues in [[!RFC3023]] section 10 for HTTP URIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended URIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data; inferences of potential medical treatments would likely require different trust than inferences for trip planning.</dd>