updated text with reserved characters
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Mon, 09 Jul 2012 13:14:04 +0100
changeset 3802 14a2dce6a071
parent 3801 ba458fbd504a
child 3803 55bf05b366d4
child 3804 03b537acb878
updated text with reserved characters
model/comments/issue-437-jun.txt
model/comments/issue-438-tom.txt
model/prov-dm.html
model/prov-n.html
--- a/model/comments/issue-437-jun.txt	Mon Jul 09 11:13:36 2012 +0100
+++ b/model/comments/issue-437-jun.txt	Mon Jul 09 13:14:04 2012 +0100
@@ -140,11 +140,19 @@
    > - I don't understand the "There may be other kinds of bundles not
    >   directly expressible by this constructor, such as napkin,
    >   whiteboard, etc." How are they being bundles?
+
+Text has been slighlty updated.
+
+"There may be other kinds of bundles not directly expressible by this constructor, such as provenance descriptions handwritten on a letter or a whiteboard, etc.  What ever the means by which bundles are expressed, all can be described, as in the following section."
+
+prov-o contains the same definition.
    > 
    > 5.5.3
    > 
    > - The narratives in this section are rather complex. But I am not
    >   going into details because it's marked as at risk at the moment.
+
+TODO
    > 
    > 5.6.
    > 
@@ -154,7 +162,8 @@
    > after these many rounds of revisions. So, well done!
    > 
    > -- Jun
-   > 
+   >
+ 
    > 
    > 
    > ----------------------------------------------------------------------
@@ -174,6 +183,9 @@
    > >> key to illustrate the purpose of this concept.
    > 
    > [...]
+
+This should now be fixed.
+
    > 
    > > Regarding your second point, I don't think it is possible. But I may
    > > be wrong.
@@ -181,6 +193,11 @@
    > We have an example of prov:tracedTo in the prov-o, which should have
    > been replaced with the new prov:wasInfluencedBy. Does that one help
    > you?
+
+I raised an issue about this example in prov-o.
+In any case, it is is similar to the one here, since it indicates the
+kind of influence taking place.
+
    > 
    > > > > 5.5.3 > - The narratives in this section are rather complex. But
    > >I am not > going into details because it's marked as at risk at the
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/model/comments/issue-438-tom.txt	Mon Jul 09 13:14:04 2012 +0100
@@ -0,0 +1,123 @@
+   > Hello Luc & others,
+   > 
+   > I have reviewed the PROV-N document over the weekend.
+   > The document is well structured, and reads well. It is very usable as
+   > an "advanced reference" when wanting to know more about one of the
+   > notations. (which is exactly its purpose I suppose)
+   > 
+   > Question for reviewers: Can the document be published as Last Call working draft?
+   > Yes, I only have minor phrasing and consistency remarks below.
+   > 
+   > Minor remarks and typos:
+   > 
+   > - 2.1 Example 2
+   > 
+   > In the following expressions, the optional activity a along with the
+   > generation and usage identifiers g2 and u1: Should be "In the
+   > following expressions, the optional activity a is specified along with
+   > the generation and usage identifiers g2 and u1:"
+   > 
+   > - 2.2 EBNF Grammar
+   > 
+   > Each expression non-terminal expression, i.e., entityExpression,
+   >  activityExpression etc., This sentence is a bit weird. Should the
+   >  first "expression" be omitted?
+   > 
+   > - 2.5 Comments
+   > typo: "cooments" (is fixed in latest editors draft I think)
+   > 
+   > - 3.1.4 - 3.1.8 
+   > 
+   > Even though the production usageExpression allows for expressions
+   > used(a2, -, -) and used(-; e2, -, -), these expressions are not valid
+   > in PROV-N, since at least one of id, entity, time, and attributes must
+   > be present.  a bit further, in 3.1.6 Start, this note is written as
+   > Note: Even though the production startExpression allows for
+   > expressions wasStartedBy(e2, -, -, -) and wasStartedBy(-; e2, -, -,
+   > -), these expressions are not valid in PROV-N, since at least one of
+   > id, trigger, starter, time, and attributes must be present.
+   >  
+
+    > This is a more general issue than just in this section. I would
+   >       be consistent here and add the "Note:" everywhere where this
+   >       type of comment is made.
+   > 
+   > Also, it seems that these notes do not always make sense.  For
+   > example, in 3.1.4, it says that at least one of id, entity, time, and
+   > attributes must be present, but that used(-; e2, -, -) is not valid,
+   > even though it contains an entity. (this was fixed in the latest
+   > editor's drfat I saw) The same issue occurs in 3.1.6 Start: At least
+   > one of id, trigger, starter, time, and attributes must be present, but
+   > wasStartedBy(e2, -, -, -) and wasStartedBy(-; e2, -, -, -) are
+   > invalid. However, a starter or a trigger is present. Did you mean: at
+   > least one of id, activity, time, and attributes must be present.?
+   > 
+   > The same happens with 3.1.7 End.  3.1.8 Invalidation has the correct
+   > remark: "at least one of id, activity, time, and attributes must be
+   > present."  (but I would add the "Note:" here as well)
+   > 
+   > 
+   > - 3.3.5 Influence Here id is the optional influence identifier, e2 is
+   > an entity identifier, e1 is the identifier for an ancestor entity that
+   > e2 depends on, and [ex:param="a"] is the optional set of attributes.
+   > 
+   > I think the use of "depends on" is a bit unlucky here, since it
+   > implies that the influenced entity/activity/agent is directly
+   > dependent on the influencing entity/activity/agent, while this is
+   > actually a lighter relation than that I think.  Just rephrasing this
+   > to something like "e1 is the identifier for an ancestor entity that e2
+   > was influenced by" solves this.
+   > 
+   > From here on everything looked fine to me :)
+   > 
+   > Congrats on a fine document!
+   > 
+   > - Tom
+   > 
+   > 
+   > 2012/7/5 Luc Moreau <[email protected]>
+   > Hi Stian and Tom,
+   > 
+   > Thanks for volunteering for reading prov-n.
+   > 
+   > Find the details below.
+   > 
+   > In addition, could you look at the two sections recently added.
+   > 
+   > http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html#extensibility
+   > http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html#media-type
+   > 
+   > Thanks,
+   > Luc
+   > 
+   > 
+   > -------- Original Message --------
+   >  Subject:	PROV-ISSUE-438 (prov-n-post-f2f3-review ): Final review before last call vote [prov-n]
+   > Resent-Date:	Fri, 29 Jun 2012 12:23:58 +0000
+   > Resent-From:	<[email protected]>
+   > Date:	Fri, 29 Jun 2012 12:23:46 +0000
+   > From:	Provenance Working Group Issue Tracker <[email protected]>
+   > Reply-To:	Provenance Working Group <[email protected]>
+   > To:	<[email protected]>
+   > 
+   > PROV-ISSUE-438 (prov-n-post-f2f3-review  ): Final review before last call vote   [prov-n]
+   > 
+   > http://www.w3.org/2011/prov/track/issues/438
+   > 
+   > Raised by: Luc Moreau
+   > On product: prov-n
+   > 
+   > 
+   > This is the issue to collect feedback on prov-n document (version created after F2F3).
+   > 
+   > Document to review is available from:
+   > 
+   > http://dvcs.w3.org/hg/prov/raw-file/default/model/releases/ED-prov-n-20120629/prov-n.html
+   > 
+   > Question for reviewers: Can the document be published as Last Call working draft?
+   > 
+   > Cheers,
+   > Luc
+   > 
+   > 
+   > 
--- a/model/prov-dm.html	Mon Jul 09 11:13:36 2012 +0100
+++ b/model/prov-dm.html	Mon Jul 09 13:14:04 2012 +0100
@@ -2525,7 +2525,7 @@
 <p>A bundle's identifier <span class="name">id</span> identifies a unique set of descriptions.</p>
 </div>
 
-<p>There may be other kinds of bundles not directly expressible by this constructor, such as napkin, whiteboard, etc.  What ever the means by which bundles are expressed, all can be described, as in the following section.</p>
+<p>There may be other kinds of bundles not directly expressible by this constructor, such as provenance descriptions handwritten on a letter or a whiteboard, etc.  What ever the means by which bundles are expressed, all can be described, as in the following section.</p>
 </section>
 
 
@@ -2894,6 +2894,11 @@
 
 <h4>Mention</h4>
 
+<p>An entity can be mentioned in a bundle, which contains some
+ descriptions about this entity. In this case, this entity in the
+bundle can be regarded as a specialization of another entity.</p>
+
+
 <div class="note">
 <p>Note: This feature is "<a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">at risk</a>" and may be removed from this specification based on feedback. Please send feedback to [email protected]</p>
 
--- a/model/prov-n.html	Mon Jul 09 11:13:36 2012 +0100
+++ b/model/prov-n.html	Mon Jul 09 13:14:04 2012 +0100
@@ -2124,7 +2124,10 @@
 <p>A PROV qualified name <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> has a more permissive syntax then XML's <code class="content"><a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-QName">QName</a></code> [[!XML-NAMES]]
 and SPARQL <code class="content"><a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/#rPrefixedName">PrefixedName</a></code> [[!RDF-SPARQL-QUERY]]. It is a PROV requirement that the concatenation of the namespace with the local part results in a valid IRI [[!IRI]]. Given that 
 ',' (comma),
+''' (single quote),
+'"' (double quote),
 ';' (semi-colon),
+':' (colon),
 '=' (equal),
 '(' (left bracket),
 ')' (right bracket),