provbib fixed incorrect dates
authorLuc Moreau <>
Tue, 20 Nov 2012 12:40:06 +0000
changeset 4837 4023ef1fee3d
parent 4835 2f1a8ca558a8
child 4838 b54b25b5c368
provbib fixed incorrect dates
--- a/model/media-type-request.txt	Tue Nov 20 11:36:30 2012 +0000
+++ b/model/media-type-request.txt	Tue Nov 20 12:40:06 2012 +0000
@@ -1,9 +1,10 @@
-6. Media Type
 The media type of PROV-N is text/provenance-notation. The content encoding of PROV-N content is UTF-8.
 Ivan Herman
 See also:
 How to Register a Media Type for a W3C Specification
 Internet Media Type registration, consistency of use
@@ -14,7 +15,7 @@
 It is recommended that PROV-N files stored on Macintosh HFS file systems be given a file type of "TEXT".
-This information that follows is being submitted to the IESG for review, approval, and registration with IANA.
+The information that follows has been submitted to the IESG for review, approval, and registration with IANA.
 Type name:
@@ -23,35 +24,42 @@
 Required parameters:
+charset — the value of charset must always be UTF-8.
 Optional parameters:
-charset — this parameter is mandatory. The value of charset is always UTF-8.
-Encoding considerations:
-The syntax of PROV-N is expressed over code points in Unicode [UNICODE5]. The encoding is always UTF-8 [UTF-8].
+Encoding considerations: 8bit
+The syntax of PROV-N is expressed over code points in Unicode [UNICODE]. The encoding is always UTF-8 [UTF-8].
 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]
 Security considerations:
 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.
 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.
 PROV-N can express data which is presented to the user, for example, by means of 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.
 PROV-N is a language for describing the provenance of things, and therefore a PROV-N document is metadata for other resources. Untrusted PROV-N documents may mislead its consumers by indicating that a third-party resource has a reputable lineage, when it has not. Provenance of PROV-N document should be sought.
 PROV-N uses qualified names mappeable to IRIs as term identifiers. Applications interpreting data expressed in PROV-N should address the security issues of Internationalized Resource Identifiers (IRIs) [RFC3987] Section 8, as well as Uniform Resource Identifier (URI): Generic Syntax [RFC3986] Section 7.
 Multiple IRIs may have the same appearance. Characters in different scripts may look similar (a Cyrillic "о" may appear similar to a Latin "o"). A character followed by combining characters may have the same visual representation as another character (LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT has the same visual representation as LATIN SMALL LETTER E WITH ACUTE). Any person or application that is writing or interpreting data in PROV-N must take care to use the IRI that matches the intended semantics, and avoid IRIs that make look similar. Further information about matching of similar characters can be found in Unicode Security Considerations [UNISEC] and Internationalized Resource Identifiers (IRIs) [RFC3987] Section 8.
 Interoperability considerations:
 There are no known interoperability issues.
 Published specification:
-PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney, Soiland-Reyes
+PROV-N: The Provenance Notation, Moreau, Missier, eds., Cheney, Soiland-Reyes, 2012.
 Applications which use this media type:
-No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.
+It may be used by any application for publishing provenance information. This format is designed to be a human-readable form of provenance.
 Additional information:
 Magic number(s):
-PROV-N documents may have the strings 'bundle' near the beginning of the document.
+PROV-N documents may have the strings 'document' near the beginning of the document.
 File extension(s):
@@ -63,7 +71,7 @@
 Person & email address to contact for further information:
[email protected]
+Ivan Herman, [email protected]
 Intended usage:
@@ -73,3 +81,5 @@
 Author/Change controller:
 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.
--- a/model/provbib.js	Tue Nov 20 11:36:30 2012 +0000
+++ b/model/provbib.js	Tue Nov 20 12:40:06 2012 +0000
@@ -25,7 +25,7 @@
           "Luc Moreau and Paolo Missier, eds."+
           "<a href=\"\"><cite>PROV-DM: The PROV Data Model</cite></a>. "+
-          "12 December 2012, Candidate Recommendation. "+
+          "11 December 2012, Candidate Recommendation. "+
           "URL: <a href=\"\"></a>",
@@ -37,7 +37,7 @@
           "Yolanda Gil and Simon Miles, eds. "+
           "<a href=\"\"><cite>Prov Model Primer</cite></a>. "+
-          "12 December 2012, Working Draft. "+
+          "11 December 2012, Working Draft. "+
           "URL: <a href=\"\"></a>.",