--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/comments/issue-274-gk.txt Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,302 @@
+ > Summary: I think the content is generally a big improvement, but there
+ > are some possible further removals, and I think there remain a number
+ > of document quality issues to be addressed before getting to last
+ > call. Hopefully, these can be considered in DM5
+ >
+ > When the content stabilizes, I may offer some alternate drafting
+ > suggestions, but I think it's in too much flux right now for that to
+ > be worthwhile.
+ >
+ > ...
+ >
+ > Re: http://dvcs.w3.org/hg/prov/raw-file/f52c0bb53dd4/model/prov-dm.html
+ > (Retrieved 2012-30-08)
+ >
+ > I'd wish to see all references to "things in the world" expunged: it's
+ > an ugly expression that begs more questions than it answers, and IMO
+ > runs the risk of confusing readers.
+
+
+Do you want to remove reference to "things" too?
+
+
+
+ >
+ > Section 1 intro: rewording in 1st 3 paras.
+ >
+ > Suggest that the provenance notation be a part 1 appendix, not a
+ > separate part/document. Drop references to ASN - it's *not* an
+ > *abstract* syntax notion; indeed, I think that very expression is an
+ > oxymoron.
+
+The WG needs to make a decision on this.
+
+My preference, at this stage, is to leave it in a separate document.
+1. Past experience has shown that readers confuse prov-dm and prov-n
+2. PROV-N definition is just a grammar, and the grammar is not useful
+ to understand prov-dm
+
+
+ >
+ > Part 2 is *not* an upgrade path. Please don't say this. (It's a
+ > refinement of use that allows provenance information from different
+ > sources to be combined in meaningful ways.)
+
+We can, though, others were supportive of the statements ...
+
+ >
+ > More text refinement in section 1.
+ >
+ >
+ > Section 2.1
+ >
+ > Saying "Activity is anything ..." is confusing. It suggests a
+ > continuant rather than an occurrent.
+
+Why not make this explicit:
+
+An activity is something that occurs and acts upon or with entities.
+
+
+ >
+ > Sub-editing would improve this.
+ >
+ >
+ > Section 2.2
+ >
+ > I think it would be clearer if generation and usage were introduced as
+ > events associated with activities. (Discussion of them being
+ > instantaneous can come in Part 2)
+
+It was agreed at F2F2 that we shouldn't introduce event in part 1.
+We followed this guidance.
+
+
+ >
+ > Introducing generation as "completed production" reads really
+ > strangely to me, and sounds as if it could be a produced artifact. I
+ > think a form like "completion of production" is clearer. Similarly
+ > for usage, something like "starting to consume".
+ >
+
+We can write:
+Generation is the completion of production of a new entity by an activity.
+
+Usage is the beginning of consumption of a new entity by an activity.
+
+
+ > Sub-editing would improve this.
+ >
+ >
+ > Section 2.3:
+ >
+ > "AccountEntity" - why not just "Account". Also, I understood this was
+ > to *be* a bundle, not a container for a bundle.
+
+To be addressed, once other editing work for WD5 is completed.
+
+The two notions (container vs bundle) are useful, for different purposes.
+To be investigated.
+
+
+ >
+ > The example given has no clear relationship to the description. I
+ > understood the key use-case here was to express provenance of
+ > procenance, and that is why we have accounts. I think that should be
+ > stated clearly; e.g.
+
+ >
+ > "An account is a bundle of provenance statements treated as an entity
+ > which may itself have some associated provenance."
+ >
+
+Subtle difference again: "... treated as an entity ..." vs " ... is an entity ..."
+
+We can definitely add "... which may itself have some associated provenance "
+
+
+ >
+ > Agents. I think the notion of responsibility here is so loose as to
+ > be of no practical value. When we say a text editor is "responsible
+ > for" crashing a computer, that's a kind of anthropomorphism, not a
+ > literal claim of responsibility. What we really mean is that the text
+ > editor caused the crash. The notion of responsibility is generally
+ > associated with duty, authority and/or accountability
+ > (cf. http://oxforddictionaries.com/definition/responsibility?view=uk).
+ > This is why persons and organizations are distinct from software
+ > agents. I suggest that the text here should "stick to the knitting":
+ > just state that these are commonly encountered kinds of agent, and
+ > leave it at that.
+
+I am not exactly sure what needs to be addressed here.
+ "accountable system" is definitely topical.
+
+
+ >
+ >
+ > Section 2.4
+ >
+ > This continues the muddle about "responsibility", until the definition
+ > of agent responsibility realtion which seems about right to me (note
+ > the phrase "accountable for" here).
+ >
+ > The use of responsibility in the description of association seems
+ > completely wrong to me.
+ >
+ > The discussion of activity association is surreal. A plan is defined
+ > previously as an "Entity", but association relates an *agent* to an
+ > activity.
+ >
+ > I think this section needs re-drafting.
+ >
+ >
+ > Section 2.5
+ >
+ > I think the intent and content of the diagram is generally good, but
+ > that its visual presentation could usefully be improved. I think it
+ > should appear as part of the introduction to section 2, not at the
+ > end.
+ >
+ >
+ > Generally in section 2, I think the examples are mostly well-chosen,
+ > but their presentation breaks up the flow of the overview; I woukd
+ > prefer that the examples were more succinct, maybe fewer, and
+ > introduced inline in the descriptive overview text. Ideally the whole
+ > overview would fit on just one or two pages (i.e. about half its
+ > current length on a printed page). The key purpose here, IMO, is to
+ > give a quick overview of how the various concepts are used together.
+ >
+ >
+ > Section 3:
+ >
+ > I don't find this example at all helpful. It requires too much effort
+ > to understand, and I find the process view vs author view is
+ > confusing. What is this section actually trying to tell the reader?
+ > I can't tell.
+ >
+ > I think a comprehensive example like this would be better sited as an
+ > appendix, rather than an interruption to the main flow of the
+ > document.
+ >
+ >
+ > Section 4.1:
+ >
+ > I find the sub-heading "Element" is confusing/unhelpful.
+ >
+ >
+ > Section 4.1.1 - verbatim repetition of text defining "Entity" already
+ > present in section - this is unhelpful.
+ >
+ > The description of the provenance notation expressions should use the
+ > same terms as are used in the template presented; i.e.. *not* "[
+ > attr=val1, ... ]" and "attributes".
+ >
+ > Don't need to say anything about disjointness of entities and
+ > activities in Part 1.
+ >
+ >
+ > Secftion 4.1.2
+ >
+ > Similar comments to section 4.1.1
+ >
+ > (But I think the simple statement "An activity is not an entity ..."
+ > is good.)
+ >
+ >
+ > Section 4.1.3
+ >
+ > Similar comments to section 4.1.1
+ >
+ > Don't need to say why sub-categories of agent are introduced.
+ >
+ > I would probably avoid making the mutual exclusivity claim (legally,
+ > it may be or become a debatable point).
+ >
+ >
+ > Section 4.1.4
+ >
+ > I don't see that notes are an essential part of the provenance
+ > structure. I'd prefer to drop them, as I don't see them adding any
+ > expressive capability.
+ >
+ >
+ > Section 4.2
+ >
+ > The table of different relation domain and range combinations is fair
+ > enough, but I'm not convinced the additional level of document
+ > structure reflecting this is useful.
+ >
+ > Ideally, I think the relations would all appear at the same document
+ > level as the concepts, so they have a similar "visual signature" when
+ > scanning the document.
+ >
+ > Most or all subsections have repetition of text from section 2 similar
+ > to that noted for section 4.1.1
+ >
+ > Also, most sections seem to suffer from a similar mismatch between the
+ > provenance notation template given and the accompanying description of
+ > the constituent elements.
+ >
+ > I think generation and usage should be described as events (not
+ > necxessarily to introduce a formal notion of events, just make it
+ > clear that they are events corresponding to some change in the
+ > relationship between an entity and an activity)
+ >
+ >
+ > Section 4.2.2.1
+ >
+ > "Responsibility" again.
+ >
+ > There are two things going on here that I feel are very muddled:
+ >
+ > (a) this rather odd notion of responsibility, and
+ >
+ > (b) associating a plan with an activity.
+ >
+ > At the very least, I think these aspects should be separated, not just
+ > lumped into an single overloaded element.
+ >
+ > I'm not sure why some expression components are explicit and possibly
+ > optional parameters, while athewrs are attributes. What's the
+ > intended difference here?
+ >
+ >
+ > Section 4.2.3.1
+ >
+ > Responsibility again. In this case, I think there may be some
+ > justification for talking about responsibility, but earlier treatment
+ > of this idea makes it hard for me to know what is really being
+ > expressed. I think it is the notion that some actions of one agent
+ > are authorized or controlled by another agent in the context of a
+ > given activity, hence any accountability for the outcome may propagate
+ > back to the controlling or authorizing agent. But that's not entirely
+ > clear to me from the text.
+ >
+ > Also, I can't tell if the structures here would accommodate different
+ > agents having different responsibilities. E.g. a manager authorizes
+ > an engineer to purchase a component, but is then instructed by the
+ > engineer in its deployment/installation... when the component fails
+ > to achieve some required outcome, who is accountable? The manager for
+ > not authorizing enough funds, or the engineer for not properly
+ > explaining how to use the component?
+ >
+ >
+ > Section 4.2.3.2
+ >
+ > Skipped - I understand this is due to be replaced. (Despite my
+ > reservations expressed elsewhere, the replacement looks like a
+ > significant improvement.)
+ >
+ >
+ > Section 4.2.3.3
+ >
+ > Do we still need Alternate and Specialization in the provenance
+ > notation?
+ >
+ > ...
+ >
+ > I'm running out of time, so I'll stop here.
+ >
+ >
+ >
+ >
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/comments/issue-274-sam.txt Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,259 @@
+ > Hello Luc,
+ >
+ >
+ >
+ > I send my review for PROV-DM again, because I am not sure you received
+ > it. Two weeks ago, I posted this to the prov mailing list, but with a
+ > different email address than the one I am listed on at W3C, because of
+ > a mail server crash. Because of this, it took some days before it was
+ > distributed to the PROV list. This is, I think, the reason my review
+ > wasn`t good received.
+ >
+ >
+ >
+ > In mean time, the mail server is up again and if you want I can send
+ > it again to the prov mailing list, this time using the right email
+ > address.
+ >
+ >
+ >
+ > Best,
+ >
+ >
+ >
+ > Sam
+ >
+ >
+ >
+ > --
+ > Sam Coppens
+ >
+ > Ghent University - IBBT
+ > Faculty of Engineering
+ > Department of Electronics and Information Systems
+ > Multimedia Lab
+ >
+ > Gaston Crommenlaan 8 bus 201
+ > B-9050 Ledeberg-Ghent
+ > Belgium
+ >
+ > t: +32 9 33 14959
+ > f: +32 9 33 14896
+ > t secr: +32 9 33 14911
+ > e: sam.coppens@ugent.be or samcoppens@hotmail.com
+ >
+ >
+ > URL: http://multimedialab.elis.ugent.be
+ >
+ >
+ >
+ > From: Sam Coppens UGent [mailto:sam.coppens@ugent.be]
+ > Sent: Thursday, March 01, 2012 10:38 AM
+ > To: 'public-prov-wg@w3.org'
+ > Subject: Review of Provenance DM documents
+ >
+ >
+ >
+ > Hello,
+ >
+ >
+ >
+ > Here is my review of the PROV-DM documents.
+ >
+ >
+ >
+ > Best,
+ >
+ >
+ >
+ > Sam
+ >
+ >
+ >
+ >
+ >
+ > In general:
+ >
+ > The overall structure of the document is very clear and things are now
+ > nicely separated (data model, its constraints and its expression in
+ > PROV-ASN). This allows to find faster the information needed.
+ >
+ > All three documents are well written and understandable. In general, I
+ > would say it is a very good improvement over the previous version
+ > where everything was in 1 document. I would recommend this version to
+ > become the editor`s draft.
+ >
+ >
+ >
+ > PROV-DM part 1:
+ >
+ >
+ >
+ > General Remarks:
+ >
+ >
+ >
+ > In Section 1 , the paragraph right in front of section 1.1 talks about
+ > an `upgrade path` to enrich simple provenance with extra
+ > descriptions. The notion of an `upgrade path` must be clarified,
+ > because it is nowhere used in the remainder of the document, neither
+ > in PROV-DM part 2. It is confusing at the moment.
+ >
+ >
+ >
+ > Section 2, Subsection2.3: AccountEntity very shortly explained
+ > here. The notion of account is better specified in PROV-DM part
+ > 2. From the provided definition here it is not clear that the
+ > provenance of the same entity can be expressed as different
+ > accounts. The definition of AccountEntity also includes ` resource`,
+ > which is quite confusing, because it is not part of the provenance
+ > terminilogy. Maybe replace it by `Entity`.
+ >
+ >
+ >
+ >
+ >
+ >
+ >
+ > Section 4, Subsection 4.1.4: `A separate PROV-DM relation is used to
+ > associate a note with something that is identifiable (see Section on
+ > annotation). A given note may be associated with multiple identifiable
+ > things.` `Things` is confusing here. It is maybe better to say entity
+ > and/or activity. `Thing` brings in some semantics.
+ >
+ >
+ >
+ > Section 5, Subsection 5.7: The added value of `Original Source` over
+ > `Traceability` is not clear. It should be better explained why we need
+ > this relation. IMO, it could be expressed as a traceability relation
+ > or a specialization of the traceability relation.
+ >
+ >
+ >
+ > Spelling Corrections:
+ >
+ >
+ >
+ > Section 2, Subsection 2.1: Activity definition: two phrases after each
+ > other are the same: `An activity is anything that can operate on
+ > entities. In particular, activities may produce, consume, or transform
+ > an entity. Activities that operate on digital entities may for example
+ > move, copy, or duplicate them. Activities that operate on digital
+ > entities may for example move, copy, or duplicate them.`
+ >
+ >
+ >
+ > Section 2, Subsection 2.2: Usage definition: Usage is the beginning on
+ > an entity being consumed by an activity. Before usage, the activity
+ > had not begun to consume or use to this entity (and could not have
+ > been affected by the entity).
+ >
+ >
+ >
+ > Section 4, Subsection 4.1.4: example: `The note is associated with the
+ > entity tr:WD-prov-dm-20111215 previously introduced (hasAnnotation is
+ > discussed in Section Annotation). The note's identifier and attributes
+ > are declares declared in a separate namespace denoted by prefix ex2.`
+ >
+ >
+ >
+ >
+ >
+ > PROV-DM part 2:
+ >
+ >
+ >
+ > General Remarks:
+ >
+ >
+ >
+ > Section 1 & Section 2: These two sections are further refinements of
+ > the already explained data model. IMO, these sections could be
+ > included in PROV-DM part 1. The event based perspective on provenance
+ > is part of the core prov-dm model. Then PROV-DM part 2 focusses on the
+ > additional constraints.
+ >
+ >
+ >
+ > Section 2, Subsection 2.2: The example of different perspectives on a
+ > resource with a URL is essential in making accounts of provenance
+ > clear. What still needs some attention in the document is the relation
+ > entity – entity record and how they are identified and which of these
+ > two identifiers are referred to when pointing to an entity. An example
+ > would make it clear. (maybe PROV-DM part 1 is a better place to
+ > explain this)
+ >
+ >
+ >
+ > Spelling Corrections:
+ >
+ >
+ >
+ > Section 4, Intro: In this section, we revisit elements and relations
+ > of PROV-DM, and examine and examine the constraints associated with
+ > their definitions.
+ >
+ >
+ >
+ > Section 4, Subsection 4.2.1: This entity become becomes available for
+ > usage after this instantaneous event.
+ >
+ >
+ >
+ > Section 4, Subsection 4.2.6: precise-1 derivation is richer than an
+ > imprecise-1 derivation, itself, being more informative that an
+ > imprecise-n derivation. Hence, the following implications hold.
+ >
+ >
+ >
+ > Section 6, Intro: We anticipate that verification algorithms could be
+ > developedm, though this verification is outside the scope of this
+ > specification.
+ >
+ >
+ >
+ >
+ >
+ > PROV-DM part 3:
+ >
+ >
+ >
+ > General Remarks:
+ >
+ >
+ >
+ > No Remarks.
+ >
+ >
+ >
+ > Spelling Corrections:
+ >
+ >
+ >
+ > Section 3, Subsection 3.2.7: `A specialization relation`s text matches
+ > the specializationExpression production.`
+ >
+ >
+ >
+ > --
+ > Sam Coppens
+ >
+ > Ghent University - IBBT
+ > Faculty of Engineering
+ > Department of Electronics and Information Systems
+ > Multimedia Lab
+ >
+ > Gaston Crommenlaan 8 bus 201
+ > B-9050 Ledeberg-Ghent
+ > Belgium
+ >
+ > t: +32 9 33 14959
+ > f: +32 9 33 14896
+ > t secr: +32 9 33 14911
+ > e: sam.coppens@ugent.be or samcoppens@hotmail.com
+ >
+ >
+ > URL: http://multimedialab.elis.ugent.be
+ >
+ >
+ >
Binary file model/images/components.png has changed
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/images/components.svg Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,232 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="302.38351"
+ height="158.71844"
+ id="svg2816"
+ version="1.1"
+ inkscape:version="0.47 r22583"
+ sodipodi:docname="components.svg"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <defs
+ id="defs2818">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 526.18109 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="744.09448 : 526.18109 : 1"
+ inkscape:persp3d-origin="372.04724 : 350.78739 : 1"
+ id="perspective2824" />
+ <inkscape:perspective
+ id="perspective3621"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ </defs>
+ <sodipodi:namedview
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="3.1582409"
+ inkscape:cx="151.19176"
+ inkscape:cy="79.359239"
+ inkscape:document-units="mm"
+ inkscape:current-layer="layer1"
+ showgrid="false"
+ inkscape:window-width="1280"
+ inkscape:window-height="1001"
+ inkscape:window-x="1280"
+ inkscape:window-y="0"
+ inkscape:window-maximized="1"
+ showborder="false"
+ inkscape:showpageshadow="false" />
+ <metadata
+ id="metadata2821">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ <dc:title></dc:title>
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1"
+ transform="translate(-45.480709,-245.16272)">
+ <rect
+ style="fill:#ff2a2a;fill-opacity:0.20171652;stroke:#f51f1f;stroke-width:1;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect2826"
+ width="203.42575"
+ height="41.663822"
+ x="45.980709"
+ y="361.71735"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="102.55271"
+ y="387.02023"
+ id="text2828"
+ sodipodi:linespacing="100%"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ sodipodi:role="line"
+ id="tspan2830"
+ x="102.55271"
+ y="387.02023">C1: entities/activities</tspan></text>
+ <path
+ style="fill:#0044aa;fill-opacity:0.20171652;stroke:#3743ff;stroke-width:0.99999994;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ d="m 166.46875,322.08344 c -1.03928,0 -1.875,0.82849 -1.875,1.85878 l 0,35.31687 c 0,1.03029 0.83572,1.85878 1.875,1.85878 l 83.15625,0 c 0.17688,0 0.33798,-0.017 0.5,-0.062 l 0,40.36656 c 0,1.03029 0.83572,1.85878 1.875,1.85878 l 45.03125,0 c 1.03928,0 1.875,-0.82849 1.875,-1.85878 l 0,-77.48025 c 0,-1.03029 -0.83572,-1.85878 -1.875,-1.85878 l -45.03125,0 c -0.46268,0 -0.86108,0.16039 -1.1875,0.43372 -0.32372,-0.26384 -0.73381,-0.43372 -1.1875,-0.43372 l -83.15625,0 z"
+ id="rect3604"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="200.06783"
+ y="338.89709"
+ id="text2828-5"
+ sodipodi:linespacing="100%"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ sodipodi:role="line"
+ id="tspan2830-6"
+ x="200.06783"
+ y="338.89709">C2: agents/</tspan><tspan
+ sodipodi:role="line"
+ x="200.06783"
+ y="352.89709"
+ id="tspan3638">responsibility</tspan></text>
+ <path
+ style="fill:#00aa00;fill-opacity:0.20171652;stroke:#07530e;stroke-width:1;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ d="m 91.291827,284.46876 c -1.028013,0 -1.885577,0.84282 -1.885577,1.89094 l 0,72.51788 c 0,1.04812 0.857564,1.89095 1.885577,1.89095 l 70.508233,0 c 1.02801,0 1.85467,-0.84283 1.85467,-1.89095 l 0,-37.91352 c 0.15729,0.0439 0.32324,0.0945 0.49457,0.0945 l 65.56246,0 c 1.02801,0 1.85467,-0.84283 1.85467,-1.89095 l 0,-32.80796 c 0,-1.04812 -0.82666,-1.89094 -1.85467,-1.89094 l -65.56246,0 c -0.45374,0 -0.88381,0.16744 -1.20553,0.44122 -0.31927,-0.26518 -0.69794,-0.44122 -1.14371,-0.44122 l -70.508233,0 z"
+ id="rect3661"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="113.17803"
+ y="308.84995"
+ id="text3666"
+ sodipodi:linespacing="100%"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ sodipodi:role="line"
+ id="tspan3668"
+ x="113.17803"
+ y="308.84995">C3: derivations</tspan></text>
+ <rect
+ style="fill:#ccff00;fill-opacity:0.20171652;stroke:#9a9617;stroke-width:1;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect3670"
+ width="42.433857"
+ height="76.250793"
+ x="46.007683"
+ y="284.41434"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="293.75912"
+ y="-65.905884"
+ id="text3672"
+ sodipodi:linespacing="100%"
+ transform="matrix(0.01389428,0.99990347,-0.99990347,0.01389428,0,0)"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ sodipodi:role="line"
+ x="293.75912"
+ y="-65.905884"
+ id="tspan3676">C4:</tspan><tspan
+ sodipodi:role="line"
+ x="293.75912"
+ y="-51.905884"
+ id="tspan3680"> alternate</tspan></text>
+ <rect
+ style="fill:#0b2828;fill-opacity:0.20171652;stroke:#7b0c0c;stroke-width:1;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect3682"
+ width="84.748047"
+ height="37.602875"
+ x="125.24542"
+ y="245.66272"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="134.16626"
+ y="263.13239"
+ id="text3684"
+ sodipodi:linespacing="100%"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ sodipodi:role="line"
+ id="tspan3686"
+ x="134.16626"
+ y="263.13239">C5:</tspan><tspan
+ sodipodi:role="line"
+ x="134.16626"
+ y="277.13239"
+ id="tspan3688">collections</tspan></text>
+ <rect
+ style="fill:#f4690e;fill-opacity:0.20171652;stroke:#ab501e;stroke-width:1.00000012;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect3690"
+ width="47.712372"
+ height="80.781319"
+ x="299.65186"
+ y="322.27066"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="323.58383"
+ y="-324.93756"
+ id="text5136"
+ sodipodi:linespacing="100%"
+ transform="matrix(0,1,-1,0,0,0)"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/components.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ sodipodi:role="line"
+ id="tspan5138"
+ x="323.58383"
+ y="-324.93756">C6: </tspan><tspan
+ sodipodi:role="line"
+ x="323.58383"
+ y="-310.93756"
+ id="tspan5140">annotations</tspan></text>
+ </g>
+</svg>
--- a/model/releases/WD-prov-dm-20120309/prov-dm.html Mon Mar 12 21:46:58 2012 +0000
+++ b/model/releases/WD-prov-dm-20120309/prov-dm.html Mon Mar 12 21:56:48 2012 +0000
@@ -2034,8 +2034,7 @@
-<p></p><div class="attributes" id="attributes-alternate">
-An <dfn title="dfn-Alternate" id="dfn-dfn-alternate">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:
+<p></p><div class="attributes" id="attributes-alternate">An <dfn title="dfn-Alternate" id="dfn-dfn-alternate">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:
<ul>
<li><span class="attribute">firstAlternate</span>: an identifier of the first of the two entities;</li>
<li><span class="attribute">secondAlternate</span>: an identifier of the second of the two entities.</li>
@@ -2053,8 +2052,7 @@
<p>
-</p><div class="attributes" id="attributes-specialization">
-A <dfn title="dfn-Specialization" id="dfn-dfn-specialization">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case (2). It has the following constituents:
+</p><div class="attributes" id="attributes-specialization">A <dfn title="dfn-Specialization" id="dfn-dfn-specialization">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case (2). It has the following constituents:
<ul>
<li><span class="attribute">specializedEntity</span>: an identifier of the specialized entity;</li>
@@ -2093,11 +2091,12 @@
be associated with a given identified object; symmetrically, multiple objects can be associated with a given note. Since notes have identifiers, they can also be
annotated. The annotation mechanism (with note and annotation) forms a key aspect of the extensibility mechanism of PROV-DM (see <a href="#extensibility-section">extensibility section</a>).</p>
-<p>An <dfn title="dfn-annotation" id="dfn-dfn-annotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:</p>
+<p><div class="attributes" id="attributes-annotation">An <dfn title="dfn-annotation" id="dfn-dfn-annotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:</p>
<ul>
<li><span class="attribute">something</span>: the identifier of something being annotated;</li>
<li><span class="attribute">note</span>: an identifier of a note.</li>
</ul>
+</div>
<div class="anexample">
<p>
--- a/model/working-copy/wd5-prov-dm-components.html Mon Mar 12 21:46:58 2012 +0000
+++ b/model/working-copy/wd5-prov-dm-components.html Mon Mar 12 21:56:48 2012 +0000
@@ -1518,7 +1518,11 @@
<section id="component4">
<h3>Component 4: Alternate Entities</h3>
-<p>This component consists of relations between two entities that refer to the same thing in the world.
+<section id="term-alternate-specialization">
+
+<h4>Alternate and Specialization</h4>
+
+<p>The purpose of this section is to introduce relations between two entities that refer to the same thing in the world.
Consider for example three entities:
</p>
<ul>
@@ -1533,24 +1537,19 @@
<ol>
- <li><span class="name">e1</span> and <span class="name">e2</span> refer to Bob in two contexts (as Facebook and Twitter users, respectively)
- <li> both of <span class="name">e1</span> and <span class="name">e2</span> are more detailed than <span class="name">e3</span>.
+ <li>e1 and e2 refer to Bob in two contexts (as Facebook and Twitter users, respectively)
+ <li> both of e1 and e2 are more detailed than e3.
</ol>
-<section id="term-alternate">
-
-<h4>Alternate</h4>
-
-
-
<p>The following two relations are introduced for expressing alternative or specialized entities. </p>
-<p><div class="attributes" id="attributes-alternate">An <dfn title="dfn-Alternate">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:
+<p><div class="attributes" id="attributes-alternate">
+An <dfn title="dfn-Alternate">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:
<ul>
<li><span class='attribute'>firstAlternate</span>: an identifier of the first of the two entities;</li>
<li><span class='attribute'>secondAlternate</span>: an identifier of the second of the two entities.</li>
@@ -1566,16 +1565,11 @@
</pre>
</div>
-</section>
-
-<section id="term-specialization">
-
-<h4>Specialization</h4>
-
<p>
-<div class="attributes" id="attributes-specialization">A <dfn title="dfn-Specialization">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case (2). It has the following constituents:
+<div class="attributes" id="attributes-specialization">
+A <dfn title="dfn-Specialization">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case (2). It has the following constituents:
<ul>
<li><span class='attribute'>specializedEntity</span>: an identifier of the specialized entity;</li>
@@ -1592,7 +1586,6 @@
</pre>
</div>
-
<!--
<p>To promote take up of these relations, it is not specified whether they are transitive or symmetric. We anticipate that applications will specialize these relations according to their needs. </p>
-->
@@ -1770,13 +1763,11 @@
annotated. The annotation mechanism (with note and annotation) forms a key aspect of the extensibility mechanism of PROV-DM (see <a
href="#extensibility-section">extensibility section</a>).</p>
-<p></p>
-<div class="attributes" id="attributes-annotation">An <dfn title="dfn-annotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:
+<p>An <dfn title="dfn-annotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:</p>
<ul>
<li><span class='attribute'>something</span>: the identifier of something being annotated;</li>
<li><span class='attribute'>note</span>: an identifier of a note.</li>
</ul>
-</div>
<div class="anexample">
<p>
--- a/model/working-copy/wd5-prov-dm-quote.html Mon Mar 12 21:46:58 2012 +0000
+++ b/model/working-copy/wd5-prov-dm-quote.html Mon Mar 12 21:56:48 2012 +0000
@@ -130,7 +130,7 @@
previousMaturity: "WD",
// if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html",
+ edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/wd5-prov-dm-quote.html",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
@@ -212,18 +212,19 @@
<p>
<span class="glossary" id="glossary-quotation">
A <dfn>quotation</dfn>
- is the repeat of an entity (such as text or image) by
-someone other that its original author.
+ is the repeat of (some or all of) an entity, such as text or image, by
+someone other than its original author.
</span>
<p>Quotation
- is a particular case of <a href="#Derivation-Relation">derivation</a> in which entity <span class="name">e2</span> is derived from an original entity <span class="name">e1</span> by copying, or "quoting", parts of it.
- A <dfn>quotation relation</dfn><span class="withPn">, written <span class="pnExpression"> wasQuotedFrom(id,e2,e1,ag,attrs)</span> in PROV-N,</span> contains:</p>
+ is a particular case of <a href="#Derivation-Relation">derivation</a> in which entity <span class="name">e2</span> is derived from an original entity <span class="name">e1</span> by copying, or "quoting", some or all of it.
+ A <dfn>quotation relation</dfn><span class="withPn">, written <span class="pnExpression"> wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the relation;</li>
-<li><span class='attribute'>quote</span>: an identifier for the entity that represents the quote (the partial copy);
-<li><span class='attribute'>original</span>: an identifier for the original entity being quoted;
-<li><span class='attribute'>originalAgent</span>: an OPTIONAL identifier for the agent to whom the original entity is attributed;
+<li><span class='attribute'>quote</span>: an identifier (<span class="name">e2</span>) for the entity that represents the quote (the partial copy);
+<li><span class='attribute'>original</span>: an identifier (<span class="name">e1</span>) for the original entity being quoted;
+<li><span class='attribute'>quoterAgent</span>: an OPTIONAL identifier (<span class="name">ag2</span>) for the agent who performs the quote;
+<li><span class='attribute'>originalAgent</span>: an OPTIONAL identifier (<span class="name">ag1</span>) for the agent to whom the original entity is attributed;
<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
</ul>
@@ -235,11 +236,12 @@
During the workshop, it became clear to me that the consensus based models (which are often graphical in nature) can not only be formalized but also be directly connected to these database focused formalizations. I just needed to get over the differences in syntax. This could imply that we could have nice way to trace provenance across systems and through databases and be able to understand the mathematical properties of this interconnection.</em>
</blockquote>
<p>If <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/"><span class="name">ex:blog</span></a> denotes the original blog by agent <span class="name">ex:Paul</a>, and
- <a href="#paul-quote"><span class="name">ex:blockquote</span></a> denotes the above paragraph, then the following descriptions express that the above paragraph is copied from a part of the blog, attributed to the agent.</p>
+ <a href="#paul-quote"><span class="name">ex:blockquote</span></a> denotes the above paragraph, then the following descriptions express that the above paragraph is copied by agent <span class="name">ex:Luc</a> from a part of the blog, attributed to the agent <span class="name">ex:Paul</a>.</p>
<pre class="codeexample">
entity(ex:blog)
+agent(ex:Luc)
agent(ex:Paul)
-wasQuotedFrom(ex:blockQuote,ex:blog,ex:Paul)
+wasQuotedFrom(ex:blockQuote,ex:blog,ex:Luc,ex:Paul)
</pre>
</pre>
@@ -277,12 +279,12 @@
<div class="anexample">
<p>
-Let us consider the current section <a href="#term-original-source"><span class="name">dm:original-source</span></a>, and
-the Google page <a href="http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html"><span class="name">go:original-source</span></a>, where the notion was originally described.
+Let us consider the current section <a href="#term-original-source"><span class="name">dm:term-original-source</span></a>, and
+the Google page <a href="http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html"><span class="name">go:credit-where-credit-is-due.html</span></a>, where the notion was originally described.
<pre class="codeexample">
-entity(dm:original-source)
-entity(go:original-source)
-hadOriginalSource(dm:original-source,go:original-source)
+entity(dm:term-original-source)
+entity(go:credit-where-credit-is-due.html)
+hadOriginalSource(dm:term-original-source,go:credit-where-credit-is-due.html)
</pre>
</div>
--- a/ontology/ProvenanceOntology.owl Mon Mar 12 21:46:58 2012 +0000
+++ b/ontology/ProvenanceOntology.owl Mon Mar 12 21:56:48 2012 +0000
@@ -754,7 +754,7 @@
<!-- http://www.w3.org/ns/prov#AgentInvolvement -->
<owl:Class rdf:about="&prov;AgentInvolvement">
- <rdfs:subClassOf rdf:resource="&prov;EntityInvolvement"/>
+ <rdfs:subClassOf rdf:resource="&prov;Involvement"/>
<prov:category>qualified</prov:category>
</owl:Class>
@@ -812,7 +812,7 @@
<!-- http://www.w3.org/ns/prov#End -->
<owl:Class rdf:about="&prov;End">
- <rdfs:subClassOf rdf:resource="&prov;Association"/>
+ <rdfs:subClassOf rdf:resource="&prov;AgentInvolvement"/>
<rdfs:subClassOf rdf:resource="&prov;InstantaneousEvent"/>
<prov:category>qualified</prov:category>
<rdfs:comment>An Agent ends an Activity, optionally at a particular TimeInstant.</rdfs:comment>
@@ -968,7 +968,7 @@
<!-- http://www.w3.org/ns/prov#Revision -->
<owl:Class rdf:about="&prov;Revision">
- <rdfs:subClassOf rdf:resource="&prov;Source"/>
+ <rdfs:subClassOf rdf:resource="&prov;EntityInvolvement"/>
<prov:category>additional</prov:category>
<rdfs:seeAlso rdf:resource="http://www.w3.org/2011/prov/wiki/ProvRDF#Revision"/>
<prov:unqualifiedForm rdf:resource="&prov;wasRevisionOf"/>
@@ -999,7 +999,7 @@
<!-- http://www.w3.org/ns/prov#Source -->
<owl:Class rdf:about="&prov;Source">
- <rdfs:subClassOf rdf:resource="&prov;Derivation"/>
+ <rdfs:subClassOf rdf:resource="&prov;EntityInvolvement"/>
<prov:category>additional</prov:category>
<rdfs:comment rdf:resource="http://www.w3.org/2011/prov/wiki/ProvRDF#Original_Source"/>
<prov:unqualifiedForm rdf:resource="&prov;hadOriginalSource"/>
@@ -1010,7 +1010,7 @@
<!-- http://www.w3.org/ns/prov#Start -->
<owl:Class rdf:about="&prov;Start">
- <rdfs:subClassOf rdf:resource="&prov;Association"/>
+ <rdfs:subClassOf rdf:resource="&prov;AgentInvolvement"/>
<rdfs:subClassOf rdf:resource="&prov;InstantaneousEvent"/>
<rdfs:comment>An Agent starts an Activity, optionally at a particular TimeInstant.</rdfs:comment>
<prov:category>qualified</prov:category>
Binary file ontology/khalid-jun-dropbox/ExampleToUseInProvo.docx has changed
Binary file ontology/khalid-jun-dropbox/PROVO (Proposal for the structure of the HTML document)-v2.docx has changed
Binary file ontology/khalid-jun-dropbox/PROVO (Proposal for the structure of the HTML document)-v3.docx has changed
Binary file ontology/khalid-jun-dropbox/PROVO_HTML_Structure_Proposal.pdf has changed
Binary file ontology/khalid-jun-dropbox/Qualified-Association.png has changed
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/khalid-jun-dropbox/README.txt Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,18 @@
+Outline of the example:
+
+Someone called Derek processed some government data about crime statistics in order to generate a graphical chart that aggregates this statistic information according to national regions. This graphical chart was used in a newspaper article.
+
+A blogger, Betty, looking at the article, spots what she thinks to be an error in the chart. Betty retrieves the provenance record of the article, how it was created in order to track the error.
+
+We provide the following example file to capture the core provenance information:
+* eg16-journalism-simple.ttl shows how the graphical chart was created through a graph generation step and a data aggregation step.
+
+For qualified relationships we provide the following example files:
+* eg16-journalism-derivation.ttl, to show how additional information about derivation can be expressed, such as when it all happened.
+
+
+* eg16-journalism-generation.ttl, to show how additional information about generation can be expressed, such as when it all happened.
+
+* eg16-journalism-usage.ttl, to show how additional information about usage can be expressed, such as when it all happened.
+
+* eg16-journalism-association.ttl, to show how we can express plan or recipe used in an activity by an agent
\ No newline at end of file
Binary file ontology/khalid-jun-dropbox/core.png has changed
Binary file ontology/khalid-jun-dropbox/diagrams.ppt has changed
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/khalid-jun-dropbox/eg16-journalism-qualified-association.ttl Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,14 @@
+### what recipe (a plan) did Dereck (an agent) follow to create the graphical chart
+
+### simple expression using prov-o core
+ex:illustrationActivity prov:wasAssociatedWith ex:derek .
+
+### more complex expression using prov-o qualified
+ex:illustrationActivity
+ prov:qualifiedAssociation [
+ a prov:Association ;
+ prov:hadPlan ex:plan1 ;
+ prov:entity ex:derek
+ ] .
+
+ex:plan1 a prov:Plan, prov:Entity .
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/khalid-jun-dropbox/eg16-journalism-qualified-derivation.ttl Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,15 @@
+#### we know that the chart was derived from the aggregated data, but what else do we know about this derivation? when did it happen etc?
+
+### The example is quite contentious at the moment because we have not settled down on derivation modeling yet.
+
+### this is what we can express using the core classes and properties
+ex:chart1 prov:wasDerivedFrom ex:aggregate1 .
+
+
+### this is what we can express using qualified relationships to talk more about the derivation relationship between the chart and the aggregated data, such as when the derivation took place, what activity was involved in the derivation
+
+ex:chart1 prov:qualifiedDerivation [
+ a prov:Derivation ;
+ prov:entity ex:aggregate1 ;
+ prov:atTime ""^^xsd:dateTime
+ ].
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/khalid-jun-dropbox/eg16-journalism-qualified-generation.ttl Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,13 @@
+#### we know that the chart was generated in a graph creation process, but what else do we know about this generation activity? when did it happen etc? what entity was used in this activity?
+
+### this is what we can express using the core classes and properties
+ex:chart1 prov:wasGeneratedBy ex:illustrationActivity .
+
+
+### this is what we can express using qualified relationships to talk more about the generation activity
+
+ex:chart1 prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:activity ex:illustrationActivity ;
+ prov:startedAtTime ""^^xsd:dateTime
+ ] .
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/khalid-jun-dropbox/eg16-journalism-qualified-usage.ttl Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,9 @@
+
+### When was the aggregated data used to create the chart?
+
+ex:illustrationActivity
+ prov:qualifiedUsage [
+ a prov:Usage ;
+ prov:entity ex:aggregate1 ;
+ prov:atTime ""^^xsd:dateTime
+ ] .
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/khalid-jun-dropbox/eg16-journalism-simple-without-comments.ttl Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,31 @@
+ex:aggregationActivity a prov:Activity ;
+ prov:used ex:dataSet1 ;
+ prov:used ex:regionList1 ;
+ prov:wasAssociatedWith ex:derek .
+
+ex:aggregate1 prov:wasGeneratedBy ex:aggregationActivity .
+
+ex:regionList1, ex:dataSet1, ex:aggregate1 a prov:Entity .
+
+ex:illustrationActivity a prov:Activity;
+ prov:used ex:aggregate1 ;
+ prov:wasAssociatedWith ex:derek .
+
+ex:illustrationActivity prov:wasInformedBy ex:aggregationActivity .
+
+ex:chart1 a prov:Entity ;
+ prov:wasGeneratedBy ex:illustrationActivity ;
+ prov:wasDerivedFrom ex:aggregate1 .
+
+ex:aggregate1, ex:chart1 prov:wasAttributedTo ex:derek .
+
+ex:derek a prov:Agent ;
+ a foaf:Person ;
+ foaf:givenName "Derek"^^xsd:string ;
+ foaf:mbox <mailto:dererk@example.org> ;
+ prov:actedOnBehalfOf ex:chartgen .
+
+ex:chartgen a prov:Agent ;
+ a prov:Organization ;
+ foaf:name "Chart Generators" .
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/khalid-jun-dropbox/eg16-journalism-simple.ttl Mon Mar 12 21:56:48 2012 +0000
@@ -0,0 +1,54 @@
+### in the first step, aggregate data by region, using raw dataset ex:dataSet1 and a list of regions ex:regionList1, and it genreated a new entity, ex:aggregated
+
+ex:aggregationActivity a prov:Activity ;
+ prov:used ex:dataSet1 ;
+ prov:used ex:regionList1 .
+
+ex:aggregate1 prov:wasGeneratedBy ex:aggregationActivity .
+
+ex:regionList1, ex:dataSet1, ex:aggregate1 a prov:Entity .
+
+### in the second step, a graphical chart was created using the aggregated data
+
+ex:illustrationActivity a prov:Activity;
+ prov:used ex:aggregate1 .
+
+ex:chart1 a prov:Entity ;
+ prov:wasGeneratedBy ex:illustrationActivity .
+
+#### so we can say that the chart was derived from the aggregated data
+
+ex:chart1 prov:wasDerivedFrom ex:aggregate1 .
+
+
+==== Agent ====
+### Derek was involved in both the aggregation and chart creation activities:
+
+ex:aggregationActivity prov:wasAssociatedWith ex:derek .
+ex:illustrationActivity prov:wasAssociatedWith ex:derek .
+
+ex:derek a prov:Agent ;
+ a foaf:Person ;
+ foaf:givenName "Derek"^^xsd:string ;
+ foaf:mbox <mailto:dererk@example.org> .
+
+==== actedOnBehalfOf ====
+
+### Derek works as part of an organization, Chart Generators, and so the provenance declares that he acts on their behalf.
+
+ex:derek prov:actedOnBehalfOf ex:chartgen .
+
+ex:chartgen a prov:Agent ;
+ a prov:Organization ;
+ foaf:name "Chart Generators" .
+
+==== wasInformedBy ====
+### the chart creation is dependent on the aggregation activity
+
+ex:illustrationActivity prov:wasInformedBy ex:aggregationActivity .
+
+==== wasAttributedTo ====
+
+### the aggregated data and the chart should all be attributed to Derek
+
+ex:aggregate1, ex:chart1 prov:wasAttributedTo ex:derek .
Binary file ontology/khalid-jun-dropbox/involvements.png has changed