Re: revised prov-dm document (ISSUE-331)

Luc,

Responding to http://dvcs.w3.org/hg/prov/raw-file/default/model/comments/issue-331-Tim.txt
Sorry for the delay.

Thanks!
Tim

------------
  > 
  > 22)
  > http://dvcs.w3.org/hg/prov/raw-file/default/model/releases/ED-prov-dm-20120402/prov-dm.html#prov-dm-concepts-and-relations
  > * suggest adding a textual indicator for the component (to readability, and to avoid potential accessibility issues for visually impaired).

I am not sure how or what, suggestion?
TL: I'd recommend adding a third column with {entities-activities, derivation, etc}.


  > * Also, the color code does not exist on the same page (one must scroll up to see it).

I don't understand.

TL: This would be fixed by adding the 3rd column above (you'd essential bake the key into the table itself, making the color decoding task moot).








------------


We may want to say that we want responsibility to stay out of the derivation component.
This would be a good refactoring I believe: we would remove agents from quotation and revision.
We would keep derivation/responsibility well distinct.

TL: I think this is worth exploring. I think it detangles some confusion. When you talk about responsibility in derivations, I'd want to reuse wasAssociatedWith on the Involvement's hadActivity.

But we shouldn't conflate responsibility and accounts.


TL:  Probably.





------------




  > 
  > 54)
  > first example in annotations
  > 
  > "The note's identifier and attributes are declared in a separate namespace denoted by prefix ex2."
  > 
  > ^^^ This seems to be insinuating some best practice without explaining
  >  why they are in different namespaces. It can lead to questions that
  >  each requires a can of worms.
  > 
  > The namespace of the attributes should NOT be in the same namespace as the instance.
  > 

I think it should. It's the rendering application that creates the note. Text changed as follows:


The note is linked to the entity tr:WD-prov-dm-20111215, with relation hasAnnotation discussed in Section 4.6.2. The note's identifier and attributes are declared in the namespace denoted by prefix ex to illustrate that the rendering application may differ from the application involving entity tr:WD-prov-dm-20111215.

TL: "ex2:instance_of_anything ex2:foo :bar" is BAD practice. Instances should NOT be defined in the same namespace as a vocabulary.
I recommend changing:
note(ex2:n1,[ex2:color="blue", ex2:screenX=20, ex2:screenY=30])
to
note(ex2:n1,[draw:color="blue", draw:screenX=20, draw:screenY=30])

same for note(ex3:n2,[ex3:reputation="excellent"]):
note(ex3:n2,[trust:reputation="excellent"])








------------
  > 
  > 
  > 
  > 57)
  > 
  > "The interpretation of any attribute declared in another namespace is out of scope."
  > 
  > ^^ does this refer to attributes mentioned in this document? 
  > 

Yes. 

TL: Recommend rephrasing "The interpretation of any attribute declared in another namespace is out of scope."
with "This specification does not provide any interpretation for any attribute declared in any other namespace."






------------
  > 
  > 
  > 
  > 58)
  > please add links to the appropriate sections for the contexts mentioned in:
  > 

  > "The attribute prov:role denotes the function of an entity with
  >     respect to an activity, in the context of a usage, generation,
  >     association, start, and end"
  > 


TODO. Tim: I don't understand: linking what to what?

TL: recommend changing : " usage, generation,
  >     association, start, and end
"
to 
 <a href="#SOMETHING">usage</a>, etc. Link to those 5.






-Tim


On Apr 17, 2012, at 11:30 AM, Luc Moreau wrote:

> 
> Dear prov-dm reviewers, dear all,
> 
> Thank you for all your inputs. Following the guidance to editors [1], we have now completed a round of editing of the prov-dm document.
> 
> All the diffs since the reviewed version are available at [2].
> 
> The latest editor's draft is available at [3].
> 
> Our response to all reviews can be found in [4 - 10].
> 
> We would be grateful if you could browse the diffs and check your concerns have been addressed.
> We are now closing ISSUE-331 pending review.
> 
> Our responses indicate that some issues will be tackled in the next draft (account, annotation, specialization).
> For other issues (e.g. responsibility, collections), it was agreed last week that it is up to individuals to raise
> separate issues on the tracker.
> 
> Regards,
> Luc
> 
> 
> [1] http://www.w3.org/2011/prov/meeting/2012-04-12#resolution_1
> 
> [2] http://dvcs.w3.org/hg/prov/raw-file/default/model/diff.html
> 
> [3] http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html
> 
> [4] http://dvcs.w3.org/hg/prov/raw-file/default/model/comments/issue-331-Jun.txt
> [5] http://dvcs.w3.org/hg/prov/raw-file/default/model/comments/issue-331-Cheney.txt
> [6] http://dvcs.w3.org/hg/prov/raw-file/default/model/comments/issue-331-Khalid.txt
> [7] http://dvcs.w3.org/hg/prov/raw-file/default/model/comments/issue-331-Satya.txt
> [8] http://dvcs.w3.org/hg/prov/raw-file/default/model/comments/issue-331-Tim.txt
> [9] http://dvcs.w3.org/hg/prov/raw-file/default/model/comments/issue-331-Curt.txt
> [10] http://dvcs.w3.org/hg/prov/raw-file/default/model/comments/issue-331-graham.txt
> 
> 
> -- 
> Professor Luc Moreau
> Electronics and Computer Science   tel:   +44 23 8059 4487
> University of Southampton          fax:   +44 23 8059 2865
> Southampton SO17 1BJ               email: l.moreau@ecs.soton.ac.uk
> United Kingdom                     http://www.ecs.soton.ac.uk/~lavm
> 
> 
>