ISSUE-585: Suggestion to avoid discussing how to 'apply' constraints; clarify what it means to 'satisfy' constraints

applying-satisfying-constraints

Suggestion to avoid discussing how to 'apply' constraints; clarify what it means to 'satisfy' constraints

State:
CLOSED
Product:
prov-dm-constraints
Raised by:
James Cheney
Opened on:
2012-10-25
Description:
A sub-issue of ISSUE-576.

From Antoine Zimmermann's email:
http://lists.w3.org/Archives/Public/public-prov-comments/2012Oct/0004.html


"""
Checking ordering, typing, and impossibility constraints

The ordering, typing, and impossibility constraints are checked rather than applied. This means that they do not generate new formulas expressible in PROV,
"""

This sentence again strongly suggests that constraints are "applied", in the sense defined previously, indicating that implementations should follow the operations mentioned previously, when in fact there is no reason to force any materialisation or "normalisastion" at all.
This is again supported by the following sentence:

"Checking such constraints follows a saturation strategy similar to that for normalization"

What follows is again dictating an implementation when everything is in fact just logical formulas that have to be consistency-checked.


...

Section 6.1

"""
A PROV instance is valid if its normal form exists and satisfies all of the validity constraints
"""

Here, it is not clear what "satisfies" means. Satisfaction is a standard term in logic, provided that a proper semantics is defined. Here, there is no proper semantics so the notion of satisfaction would have to be defined. Assuming that PROV statements are indeed mapped to FOL, and constraints expressed as FOL axioms, then the standard notion of "satisfaction" would not work here. For example, the empty document doesn't satisfy any of the constraints (an empty FOL theory only satisfies tautologies, a.k.a., valid formulas, in the usual logical sense of "valid").

There wouldn't be any problem and it would be very much shorter with a proper first order semantics.
Related Actions Items:
No related actions
Related emails:
  1. Re: PROV-WG response to comments on constraints (from jcheney@inf.ed.ac.uk on 2012-11-06)
  2. Re: PROV-WG response to comments on constraints (from jcheney@inf.ed.ac.uk on 2012-11-01)
  3. Re: PROV-WG response to comments on constraints (from antoine.zimmermann@emse.fr on 2012-11-01)
  4. PROV-WG response to comments on constraints (from jcheney@inf.ed.ac.uk on 2012-11-01)
  5. Re: Reminder: Review of responses to PROV-CONSTRAINTS public comments (from l.moreau@ecs.soton.ac.uk on 2012-11-01)
  6. Re: Reminder: Review of responses to PROV-CONSTRAINTS public comments (from jcheney@inf.ed.ac.uk on 2012-11-01)
  7. Re: Reminder: Review of responses to PROV-CONSTRAINTS public comments (from l.moreau@ecs.soton.ac.uk on 2012-11-01)
  8. Re: Reminder: Review of responses to PROV-CONSTRAINTS public comments (from jcheney@inf.ed.ac.uk on 2012-11-01)
  9. Re: Reminder: Review of responses to PROV-CONSTRAINTS public comments (from p.t.groth@vu.nl on 2012-11-01)
  10. Re: Reminder: Review of responses to PROV-CONSTRAINTS public comments (from jcheney@inf.ed.ac.uk on 2012-10-31)
  11. Re: Reminder: Review of responses to PROV-CONSTRAINTS public comments (from l.moreau@ecs.soton.ac.uk on 2012-10-31)
  12. Reminder: Review of responses to PROV-CONSTRAINTS public comments (from jcheney@inf.ed.ac.uk on 2012-10-31)
  13. Re: Review of PROV-CONSTRAINTS issues (ISSUE-582, ISSUE-579, ISSUE-585, ISSUE-583) (from Paolo.Missier@ncl.ac.uk on 2012-10-29)
  14. Review of PROV-CONSTRAINTS issues (ISSUE-582, ISSUE-579, ISSUE-585, ISSUE-583) (from jcheney@inf.ed.ac.uk on 2012-10-26)
  15. PROV-ISSUE-585 (applying-satisfying-constraints): Suggestion to avoid discussing how to 'apply' constraints; clarify what it means to 'satisfy' constraints [prov-dm-constraints] (from sysbot+tracker@w3.org on 2012-10-25)

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