W3C home > Mailing lists > Public > public-prov-wg@w3.org > November 2011

Re: PROV-ISSUE-134: Non-Human Agent vs. Human Agent [Data Model]

From: Reza B'Far (Oracle) <reza.bfar@oracle.com>
Date: Wed, 30 Nov 2011 10:28:28 -0800
Message-ID: <4ED675CC.4040008@oracle.com>
To: public-prov-wg@w3.org
Thanks Luc.  Yes, issue has been addressed.

On 11/30/11 5:00 AM, Luc Moreau wrote:
> Hi Reza,
> The latest WD now includes SoftwareAgent, People, and Institutions as 
> subclasses of Agent.
> I believe this addresses your issue. I am closing this issue, pending 
> review.
> Best regards,
> Luc
> On 10/24/2011 12:04 AM, Provenance Working Group Issue Tracker wrote:
>> PROV-ISSUE-134: Non-Human Agent vs. Human Agent [Data Model]
>> http://www.w3.org/2011/prov/track/issues/134
>> Raised by: Reza B'Far
>> On product: Data Model
>> I propose to revisit the previously discussed, but not concluded, 
>> topic of "Types" of Agents.  I had brought up this topic and the 
>> following was suggested as a reference -
>> http://sourceforge.net/apps/mediawiki/trdf/nfs/project/t/tr/trdf/7/7a/ProvenanceVocabularyOverview.png 
>> There are a large set of use-cases (not just in my particular 
>> interest of Governance) where, whether the actions of an agent are 
>> directly controlled by a human being versus an automated mechanism 
>> makes a very significant difference in inferencing over the available 
>> instance data.  Examples:
>> 1.  Human agent modifying a legal document versus the legal document 
>> being modified by a system agent that converts data formats.
>> 2.  Human agent modifying a setting in a system whose provenance 
>> model is important for governing that system versus a system agent 
>> doing the same:  Example - Provenance of a "License" where Human 
>> agent expiring a license by changing/enforcing a date is quite a 
>> different event than a system agent changing/enforcing a date (say as 
>> a part of a mass/cascade update to a series of records) that causes 
>> expiration of a license.
>> Other use-cases are available if need-be.  I actually claim that the 
>> number of such use-cases are increasing given the proliferation of 
>> pipe-and-filter architectures being deployed within Big Data 
>> infrastructures (where either pipes or filters can be Non-Human 
>> Agent/Actors).  Furthermore, as another evidence, there are other 
>> references to UML Use-Case and Sequence Diagrams where the 
>> distinction is becoming prevalent.
>> As a solution, I suggest we take the same approach that the 
>> aforementioned URL above has taken.
Received on Wednesday, 30 November 2011 18:29:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:51:04 UTC