--- a/model/prov-n.html Mon Nov 19 10:49:19 2012 +0000
+++ b/model/prov-n.html Mon Nov 19 14:07:41 2012 +0000
@@ -199,7 +199,7 @@
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
+ specStatus: "CR",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "prov-n",
@@ -207,10 +207,10 @@
// if your specification has a subtitle that goes below the main
// formal title, define it here
// subtitle : "About-to-be-frozen WD4 (for internal release)",
- subtitle : "<a href=\"diff-n.html\">Diffs</a> since LC Release ",
+ //subtitle : "<a href=\"diff-n.html\">Diffs</a> since LC Release ",
// if you wish the publication date to be other than today, set this
- // publishDate: "2012-12-11",
+ publishDate: "2012-12-11",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -225,7 +225,7 @@
edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html",
// if this is a LCWD, uncomment and set the end of its review period
- lcEnd: "2012-09-18",
+ crEnd: "2013-01-31",
// if you want to have extra CSS, append them to this list
// it is recommended that the respec.css stylesheet be kept
@@ -2047,14 +2047,14 @@
<div class="anexample" id="anexample-value">
<p>
-The following examples respectively are the string "abc", the string (in French) "bonjour", the integer number 1, and the IRI "http://example.org/foo".
+The following examples respectively are the string "abc", the string (in French) "bonjour", the integer number 1, and the IRI "http://example.org/foo".</p>
<pre class="codeexample">
"abc"
"bonjour"@fr
"1" %% xsd:integer
"http://example.org/foo" %% xsd:anyURI
</pre>
-The following examples are the floating point number 1.01 and the boolean true.
+<p>The following examples respectively are the floating point number 1.01 and the boolean true.</p>
<pre class="codeexample">
"1.01" %% xsd:float
"true" %% xsd:boolean
@@ -2375,7 +2375,7 @@
Note that the generic <code class="content"><a class="grammarRef"
href="#prod-extensibilityExpression">extensibilityExpression</a></code> production above allows for alternative notations to be used for expressing membership, if the designers of the extensions so desire. Here is an alternate syntax that is consistent with the productions:
<pre class="codeexample">
- prefix dictExt <http://example.org/dictionaries>
+ prefix dictExt <http://example.org/dictionaries#>
dictExt:hadMembers(mid; d, dictExt:set(dictExt:pair("k1",e1),
dictExt:pair("k2",e2),
dictExt:pair("k3",e3)),
@@ -2498,6 +2498,7 @@
<li> <a href="http://www.w3.org/2011/prov/track/issues/573">ISSUE-573</a>: Updated Media Type section.
<li> <a href="http://www.w3.org/2011/prov/track/issues/589">ISSUE-589</a>: Updated scoping rule for prefix-namespace declaration. Also refrained from saying bundles are self-contained.
<li> Moved feature at Risk mention into a separate note.
+<li> Editorial's pass pre-publication.
</ul>
</section>