Re: PROV-ISSUE-605 (fpwd-prov-overview): reviews of prov-overview for fpwd [PROV-OVERVIEW]

- Can this document be released as FPWD?
     yes
- If yes, are there other issues to work on?

issues are all minor:

-  shouldn't PROV-DC be part of the list as a note?

- PROV-O is listed before PROV-DM everywhere they are mentioned together ( also in the table of sec. 2). but initially PROV-O is 
defined as "a mapping from PROV to ..."  which suggests it follows PROV-DM. This is reinforced by the structuring in the figure, 
where PROV-DM is central.

- "This instantiated"  -> "This is instantiated"

- "developers and user " -> "developers and users"

- in the figure, the positioning of blocks without explicit relationships amongst them seems a bit arbitrary. for instance, why 
would prov-links and prov-dc be at the bottom at the same level?

sec 2

- "In order to use PROV, one need not be familiar with all of these documents. Indeed, PROV was specifically designed so that simple 
usage would always be compatible with more advanced usage scenarios."
    this reads a bit odd.
      Suggestion: postpone this point until after the list of audiences, then replace the text above with smt along the lines of
   "The PROV documents are designed so that users and developers may get started quickly with basic usage of PROV, and then 
incrementally progress to more advanced usage scenarios"

- "a notation for provenance aimed at human consumption."
   suggest replacing with
    a human-readable notation for provenance"

- "one of the many applications that support it."
     many?

--Paolo


-- 
-----------  ~oo~  --------------
Paolo Missier - Paolo.Missier@newcastle.ac.uk, pmissier@acm.org
School of Computing Science, Newcastle University,  UK
http://www.cs.ncl.ac.uk/people/Paolo.Missier