W3C home > Mailing lists > Public > public-prov-wg@w3.org > May 2012

ISSUE-385: hasProvenanceIn: finding a solution

From: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
Date: Thu, 31 May 2012 22:54:08 +0100
Message-ID: <EMEW3|ccfb9b3e27833e142419040f7fa6bbdbo4UMsE08L.Moreau|ecs.soton.ac.uk|4FC7E880.6070303@ecs.soton.ac.uk>
To: Provenance Working Group WG <public-prov-wg@w3.org>

To try and converge towards a solution, I am
circulating an example using a ternary hasProvenanceIn.
I would like to understand if and how we can make it work with
a simpler relation.

Two bundles ex:run1 and ex:run2 describe bob's role as a controller
of two activities.  Same bob, two different bundles.

     bundle ex:run1
      activity(ex:a1, 2011-11-16T16:00:00,2011-11-16T17:0:00)  
//duration: 1hour

     bundle ex:run2
      activity(ex:a2, 2011-11-17T10:00:00,2011-11-17T17:0:00)  
//duration: 7hours

A performance analysis tool rates the performance of agents (this could 
be used
to dispatch further work to performant agents, or congratulate them, etc).

     bundle tool:analysis01

       agent(tool:Bob1, [perf:rating="good"])
       hasProvenanceIn(tool:Bob1, ex:run1, ex:Bob)  // Bob performance 
in ex:run1 is good

       agent(tool:Bob2, [perf:rating="bad"])
       hasProvenanceIn(tool:Bob2, ex:run2, ex:Bob)  // Bob performance 
in ex:run2 is bad


The performance analysis tool has to rate two involvements of ex:Bob in 
two separate activities.
Two specialized version of ex:Bob are defined: tool:bob1 and tool:bob2, 
with rating good and
bad respectively.

tool:Bob1 is linked to ex:Bob in run1, and tool:Bob2 is linked to ex:Bob 
in run2, with the following

       hasProvenanceIn(tool:Bob1, ex:run1, ex:Bob)
       hasProvenanceIn(tool:Bob2, ex:run2, ex:Bob)

Nothing is expressed about ex:Bob in bundle tool:analysis01 (except that 
this is an alias
for tool:Bob1 and tool:Bob2).

It is suggested that the ternary relation could be replaced by
isTopicIn(tool:Bob1, ex:run1)
specialization(tool:Bob1, ex:Bob).

I don't understand the point of
   isTopicIn(tool:Bob1, ex:run1)
since tool:Bob1 is not a topic in ex:run1.

Also, we now seem to have made ex:Bob a topic of tool:analysis01, because
the following expression.
specialization(tool:Bob1, ex:Bob).

 From tool:analysis01, where do I find provenance about ex:Bob?
It look like this has become a dead end in this graph.

Do I need to introduce:
   isTopicIn(ex:Bob, ex:run1)
   isTopicIn(ex:Bob, ex:run2)?

So now we would  have:
isTopicIn(tool:Bob1, ex:run1)
specialization(tool:Bob1, ex:Bob)
isTopicIn(tool:Bob2, ex:run2)
specialization(tool:Bob2, ex:Bob)
isTopicIn(ex:Bob, ex:run1)
isTopicIn(ex:Bob, ex:run2)

Which means that:

specialization(tool:Bob1, ex:Bob)
isTopicIn(ex:Bob, ex:run2)

... would lead us to believe that good rating is due to slow performance.

Can the proposer of the separate binary relations explain how this 
example can work?

Received on Thursday, 31 May 2012 21:54:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 31 May 2012 21:54:53 GMT