ISSUE-343: Objections regarding Account


Objections regarding Account

Raised by:
Timothy Lebo
Opened on:
This issue serves as a place holder for a variety of issues regarding the account section of dm-constraints.

The underlying cause for this group of issues is that Accounts would not be permitted to span the "specialization hierarchy" like other entities can, similar to the "Different users may take different perspectives on a resource with a URL" example. One should have the freedom to apply perspectives to what an Account is, and the current definitions prevent that.

The following adjustments would help to address some of my concerns:

"An account is as a container of provenance descriptions, hence its content MAY change over time."
"An account is a bundle of provenance descriptions whose content MAY change over time."

"If an account's set of descriptions changes over time, it increases monotonically with time."
"If an account's set of descriptions changes over time, it SHOULD increase monotonically with time."

I cannot agree to the following:

"A given description of e.g. an entity in a given account, in terms of its identifier and attribute-value pairs, does not change over time."

nor the Notes:

The last point is important. It indicates that within an account:

It is always possible to add new provenance descriptions, e.g. stating that a given entity was used by an activity, or derived from another. This is very much an open world assumption.
It is not permitted to add new attributes to a given entity (a form of closed world assumption from the attributes point of view), though it is always permitted to create a new description for an entity, which is a "copy" of the original description extended with novel attributes (cf Example merge-with-rename).

Being forced to "write only once" about an entity is too restrictive. The account maintainer should be aware of the characterization interval and respect it and know when they are talking about the same entity or when it's a slightly different entity that warrants a truly distinct entity. If the _same_ entity had an additional fixed attribute that was simply unknown at "first write", the maintainer should not be required to duplicate the original entity just to update their description.
Related Actions Items:
No related actions
Related emails:
  1. Re: PROV-ISSUE-343 (account-objections): Objections regarding Account [prov-dm-constraints] (from on 2012-07-18)
  2. Re: PROV-ISSUE-343 (account-objections): Objections regarding Account [prov-dm-constraints] (from on 2012-05-21)
  3. Re: PROV-ISSUE-343 (account-objections): Objections regarding Account [prov-dm-constraints] (from on 2012-05-21)
  4. Re: PROV-ISSUE-333 (review-prov-dm-constraints-wd5): issue to collect feedback on prov-dm-constraints wd5 [prov-dm-constraints] (from on 2012-04-11)
  5. PROV-ISSUE-343 (account-objections): Objections regarding Account [prov-dm-constraints] (from on 2012-04-11)

Related notes:

No additional notes.

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 343.html,v 1.1 2013-06-20 07:37:37 vivien Exp $