RE: acknowledging PROV responses


My responses to the last 3 items in your list are below.


1.1.26 ISSUE-509 (AttributesInUML)<> - no further comment

1.1.27 ISSUE-526 (Alternate)<>
The text in the working group's response to this comment (see below) is helpful.  It might be beneficial to add this to the DM document.

"Note that alternateOf is a necessarily very general relationship that, in reasoning, only tells you that the two alternate entities fix different aspects of some common thing (possibly evolving over time), and so there is some relevant connection between the provenance of the alternates. In a specific application context, alternateOf, or a subtype of it, could allow you to infer more."

1.1.28 ISSUE-502 (Derivation)<>
In my opinion, the initial emphasis on transformation may muddle the definition.  The working group's response contained a helpful phrase ("The focus of derivation is on connecting a generated entity to a used entity.") that would add clarity to the definition of derivation.

From: [] On Behalf Of Paul Groth
Sent: Wednesday, October 17, 2012 1:41 PM
To: Freimuth, Robert, Ph.D.
Subject: acknowledging PROV responses

Dear Bob,

As you have seen we've been slowly working through your issues. A key thing for the working group going forward is to record your acknowledgement of the resolution, whether it satisfies your concern or not and if not why.

Because you had quite a number of issues, I think it's best to list them out. You'll find the list below and is taken from the page:

Each issue is linked back to the response. Maybe the best way is for issues that you are happy with the resolution to just list them out and state that you are fine with how they are dealt with. We can then maybe get your other responses to the other issues.

Thanks again for your detailed feedback on PROV. It's helping us make a better specification.



  *   1.1.1 ISSUE-532 (Role)<>
  *   1.1.2 ISSUE-525 (Specialization/Alternate)<>
  *   1.1.3 ISSUE-507 (Inverse Relations)<>
  *   1.1.4 ISSUE-504 (collection/bundle)<>
  *   1.1.5 ISSUE-503 (adopt plan)<>
  *   1.1.8 ISSUE-500 (activity hierarchy)<>
  *   1.1.9 ISSUE-505 (prov-n notation)<>
  *   1.1.10 ISSUE-508 (Table 5)<>
  *   1.1.11 ISSUE-531 (Multiple location)<>
  *   1.1.12 ISSUE-528 (MentionOf)<>
  *   1.1.13 ISSUE-517 (Revision/Quotation)<>
  *   1.1.14 ISSUE-501 (DrivingACarToBoston)<>
  *   1.1.15 ISSUE-516 (DerivationAsBundle)<>
  *   1.1.16 ISSUE-514 (Starter/EnderActivity)<>
  *   1.1.17 ISSUE-513 (StartSubActivity)<>
  *   1.1.18 ISSUE-511 (UsageSubActivity)<>
  *   1.1.19 ISSUE-510 (GenerationSubActivity)<>
  *   1.1.20 ISSUE-512 (FinePayingExample)<>
  *   1.1.21 ISSUE-497 (Figure 1)<>
  *   1.1.22 ISSUE-515 (Invalidation)<>
  *   1.1.23 ISSUE-530 (attributes)<>
  *   1.1.24 ISSUE-520 (Person/Organization/SoftwareAgent)<>
  *   1.1.25 ISSUE-522 (Activity Delegation)<>
  *   1.1.26 ISSUE-509 (AttributesInUML)<>
  *   1.1.27 ISSUE-526 (Alternate)<>
  *   1.1.28 ISSUE-502 (Derivation)<>

Dr. Paul Groth (<>)
Assistant Professor
- Knowledge Representation & Reasoning Group |
  Artificial Intelligence Section | Department of Computer Science
- The Network Institute
VU University Amsterdam

Received on Friday, 26 October 2012 02:38:27 UTC