ISSUE-156: information flow ordering record - no temporal constraints?
TLebo
information flow ordering record - no temporal constraints?
- State:
- CLOSED
- Product:
- prov-dm
- Raised by:
- Timothy Lebo
- Opened on:
- 2011-11-21
- Description:
- According to 6.3 Activity Ordering Record
"wasInformedBy" is:
"An information flow ordering record is a representation that an entity was generated by an activity, before it was used by another activity."
But the only constraint does not include the temporal aspects described above:
"Given two activity records identified by a1 and a2, the record wasInformedBy(a2,a1) holds, if and only if there is an entity record identified by e and sets of attribute-value pairs attrs1 and attrs2, such that wasGeneratedBy(e,a1,attrs1) and used(a2,e,attrs2) hold."
Does the temporal constraint fall out of constraints that apply to wasGeneratedBy and used?
* If so, could this be made explicit?
* If not, can "attrs1" and "attrs2" be elaborated to include the "time used" and "time generated" AND their constrained ordering?
Thanks,
Tim
- Related Actions Items:
- No related actions
- Related emails:
- Re: PROV-ISSUE-156 (TLebo): information flow ordering record - no temporal constraints? [Data Model] (from L.Moreau@ecs.soton.ac.uk on 2011-12-02)
- Re: PROV-ISSUE-156 (TLebo): information flow ordering record - no temporal constraints? [Data Model] (from lebot@rpi.edu on 2011-12-02)
- Re: PROV-ISSUE-156 (TLebo): information flow ordering record - no temporal constraints? [Data Model] (from L.Moreau@ecs.soton.ac.uk on 2011-11-30)
- Re: PROV-ISSUE-156 (TLebo): information flow ordering record - no temporal constraints? [Data Model] (from L.Moreau@ecs.soton.ac.uk on 2011-11-21)
- PROV-ISSUE-156 (TLebo): information flow ordering record - no temporal constraints? [Data Model] (from sysbot+tracker@w3.org on 2011-11-21)
Related notes:
email is not getting picked up by the tracker: repeating here:
(reposting to list so that the tracker finds it - I updated the diagram and phrasing, too.)
Luc,
Thank you for adding the time constraint. I illustrated it with a red line in the diagram below.
I'm curious if another constraint should be added.
Nothing is stating that the usage event must follow the generation event.
Regards,
Tim
http://dvcs.w3.org/hg/prov/raw-file/f8c191710aad/diagrams/activity-ordering-records-information-flow-ordering.png
Display change log
