--- a/model/grammar/Makefile Tue Jul 03 09:31:28 2012 +0100
+++ b/model/grammar/Makefile Tue Jul 03 10:19:10 2012 +0100
@@ -34,7 +34,7 @@
do.ll.js: ll.provn do.ll.html
@echo "grammar_string= " > $(OUT.JS)
- @cat $(IN.HTML) | sed -e "s/\d039/\\\'/g" | sed -e "s/prod-prov_n_LL/prod/g" | sed -e "s/term-prov_n_LL/prod/g" | sed -e "s/((/(/g" | sed -e "s/))/)/g" | sed -e "s/timeZZ/time/g" | sed -e "s/\d035prod-PN_PREFIX/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rPN_LOCAL/g" | sed -e "s/\d035prod-PN_CHARS_U/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rPN_CHARS_U/g" | sed -e "s/\d035prod-ECHAR/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rECHAR/g" | sed -e "s/\d035prod-STRING_LITERAL2/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rSTRING_LITERAL2/g" | sed -e "s/\d035prod-STRING_LITERAL_LONG2/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rSTRING_LITERAL_LONG2/g" | sed -e "s/\d035prod-LANGTAG/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rLANGTAG/g" | sed -e "s/\d035prod-IRI_REF/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rIRI_REF/g" | sed -e "s/\d035prod-PN_CHARS\"/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rPN_CHARS\"/g" > $(IN2.HTML)
+ @cat $(IN.HTML) | sed -e "s/\d039/\\\'/g" | sed -e "s/prod-prov_n_LL/prod/g" | sed -e "s/term-prov_n_LL/prod/g" | sed -e "s/((/(/g" | sed -e "s/))/)/g" | sed -e "s/timeZZ/time/g" | sed -e "s/\d035prod-PN_PREFIX/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rPN_LOCAL/g" | sed -e "s/\d035prod-PN_CHARS_U/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rPN_CHARS_U/g" | sed -e "s/\d035prod-ECHAR/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rECHAR/g" | sed -e "s/\d035prod-STRING_LITERAL2/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rSTRING_LITERAL2/g" | sed -e "s/\d035prod-STRING_LITERAL_LONG2/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rSTRING_LITERAL_LONG2/g" | sed -e "s/\d035prod-LANGTAG/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rLANGTAG/g" | sed -e "s/\d035prod-IRI_REF/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rIRI_REF/g" | sed -e "s/\d035prod-PN_CHARS\"/http:\d047\d047www.w3.org\d047TR\d047rdf-sparql-query\d047\d035rPN_CHARS\"/g" | sed -e "s/\d035prod-DATETIME\"/http:\d047\d047www.w3.org\d047TR\d047xmlschema11-2\d047\d035nt-dateTimeRep\"/g" > $(IN2.HTML)
@cat $(IN2.HTML) | awk '{ print "'\''" $$0 " '\'' + " }' >> $(OUT.JS)
@echo "' ' ;" >> $(OUT.JS)
--- a/model/grammar/yack/prov-n-LL.bnf Tue Jul 03 09:31:28 2012 +0100
+++ b/model/grammar/yack/prov-n-LL.bnf Tue Jul 03 10:19:10 2012 +0100
@@ -150,7 +150,7 @@
-[49] timeZZ::= ISODATETIME
+[49] timeZZ::= DATETIME
@@ -201,7 +201,7 @@
DIGIT::=[0-9]
-ISODATETIME::= DIGIT DIGIT DIGIT DIGIT "-" DIGIT DIGIT "-" DIGIT DIGIT "T" DIGIT DIGIT ":" DIGIT DIGIT ":" DIGIT DIGIT ("." DIGIT (DIGIT DIGIT?)?)? ("Z" | TIMEZONEOFFSET)?
+DATETIME::= DIGIT DIGIT DIGIT DIGIT "-" DIGIT DIGIT "-" DIGIT DIGIT "T" DIGIT DIGIT ":" DIGIT DIGIT ":" DIGIT DIGIT ("." DIGIT (DIGIT DIGIT?)?)? ("Z" | TIMEZONEOFFSET)?
TIMEZONEOFFSET::= ("+" | "-") DIGIT DIGIT ":" DIGIT DIGIT;
--- a/model/prov-n.html Tue Jul 03 09:31:28 2012 +0100
+++ b/model/prov-n.html Tue Jul 03 10:19:10 2012 +0100
@@ -2332,9 +2332,6 @@
<table class="grammar">
<tbody class="grammar-ref" data-ref="prod-time"></tbody>
-<tbody class="grammar-ref" data-ref="prod-DIGIT"></tbody>
-<tbody class="grammar-ref" data-ref="prod-ISODATETIME"></tbody>
-<tbody class="grammar-ref" data-ref="prod-TIMEZONEOFFSET"></tbody>
</table>
@@ -2597,7 +2594,7 @@
<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>PROV-N is a general-purpose language for describing the provenance of things; applications may evaluate given data to infer more descriptions 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>
- <dd>PROV-N is used to express arbitrary application data; security considerations will vary by domain of use. Security tools and protocols applicable to text (e.g. PGP encryption, MD5 sum validation, password-protected compression) may also be used on PROV-N documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information.</dd>
+ <dd>PROV-N is used to express the provenance of arbitrary application data; security considerations will vary by domain of use. Security tools and protocols applicable to text (e.g. PGP encryption, MD5 sum validation, password-protected compression) may also be used on PROV-N documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information. In particular, it is noted that a given data item and the provenance for that data item may be assigned different access control policies. </dd>
<dd>PROV-N can express data which is presented to the user, for example, label attributes. Application rendering strings retrieved from untrusted PROV-N documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([[!RFC3023]] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
<dd>PROV-N uses qualified names mappeable to IRIs as term identifiers. Applications interpreting data expressed in PROV-N should address the security issues of
<a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [[!RFC3987]] Section 8, as well as
@@ -2628,17 +2625,17 @@
<dt>File extension(s):</dt>
<dd>".pn"</dd>
<dt>Base URI:</dt>
- <dd>None</dd>
+ <dd>There are no constructs in the PROV-N Syntax to change the Base IRI.</dd>
<dt>Macintosh file type code(s):</dt>
<dd>"TEXT"</dd>
<dt>Person & email address to contact for further information:</dt>
- <dd>Ivan Herman, ivan@w3.org</dd>
+ <dd>public-prov-comments@w3.org</dd>
<dt>Intended usage:</dt>
<dd>COMMON</dd>
<dt>Restrictions on usage:</dt>
<dd>None</dd>
<dt>Author/Change controller:</dt>
- <dd>The PROV-N specification is the product of Luc Moreau and Paolo Missier. A W3C Working Group may assume maintenance of this document; W3C reserves change control over this specifications.</dd>
+ <dd>The PROV-N specification is the product of the World Wide Web Consortium's PROV Working Group. The W3C has change control over this specification.</dd>
</dl>
</section>