ISSUE-243: how to interpret ASN assertions with incomplete arity?

TLebo

how to interpret ASN assertions with incomplete arity?

State:
CLOSED
Product:
prov-n
Raised by:
Timothy Lebo
Opened on:
2012-02-06
Description:
wasGeneratedBy is defined as arity 5.

The DM asserts in a rule (I've changed the variables):

wasGeneratedBy(a,b,c)

is c a(n) 1) Activity 2) Time 3) attribute-values?

The answer is intended to be 3), but it is clearly ambiguous without context.

I propose to include parameter omissions explicitly in ASN statements:

wasGeneratedBy(a,b,[],[],c)

Thanks,
Tim


Related Actions Items:
No related actions
Related emails:
  1. Re: PROV-ISSUE-243 (TLebo): how to interpret ASN assertions with incomplete arity? (from lebot@rpi.edu on 2012-03-28)
  2. Re: PROV-ISSUE-243 (TLebo): how to interpret ASN assertions with incomplete arity? (from L.Moreau@ecs.soton.ac.uk on 2012-03-28)
  3. Re: PROV-ISSUE-243 (TLebo): how to interpret ASN assertions with incomplete arity? (from Paolo.Missier@ncl.ac.uk on 2012-02-06)
  4. PROV-ISSUE-243 (TLebo): how to interpret ASN assertions with incomplete arity? (from sysbot+tracker@w3.org on 2012-02-06)

Related notes:

closed by Tim, will re-raise if it is a concern in next review.

Timothy Lebo, 28 Mar 2012, 17:35:50

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 <w3t-sys@w3.org>.
$Id: 243.html,v 1.1 2013-06-20 07:37:30 vivien Exp $