PROV Constraints to OWL
Comments
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
£
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
|
 
Still loading...
ABCDEFGHIJ
1
TypeNoNameDetailedTo be included?Where? (prov-o.owl, prov-constraints.owl, rules.sparql, n/a)Who?How?Comments?Jun's proof of concept using Pellet
2
Definition1optional-identifiersNoImplied by RDF
3
Definition2optional-attributesNoImplied by RDF
4
Definition3definition-short-formsSee commentImplied by RDFNeed: wasGeneratedBy <-> qualifiedGeneration etc; Cannot be expressed using OWL (Jun)
5
Definition4optional-placeholdersYesprov-constraints.owlexists/cardinalityJun: I am not sure we need existential quantification here. Which property do you refer to specifically?
6
Inference5communication-generation-use-inferencewasInformedBy (used,wasGeneratedBy)?rulecannot be implemented in owl using property chain
7
Inference6generation-use-communication-inference?ruleNo
8
Inference7entity-generation-invalidation-inferenceIf it's an entity, there is a generation and invalidationYesprov-constraints.owlexists/cardinality on qualifiedGeneration/InvalidationJun: why on these properties, but not on the Entity class?No
9
Inference8activity-start-end-inferenceIf it's an activity, there is a start and endYesprov-constraints.owlexists/cardinality on qualifiedStart/EndJun: why not on the Activity Class?No
10
Inference9wasStartedBy-inferencewasStartedBy->wasGeneratedBy?property chain or ruleJun: Does wasStartedBy (a,e, a1) also imply used(a,e) and wasGeneratedBy(e,a1)? Why part of it was not covered in James' rules? More discussion. Khalid: the entity e seems to be optional according to prov-dm, which means teh inference can only be made when e is specified.No?
11
Inference10wasEndedBy-inferencewasEndedBy->wasGeneratedBy?property chain or ruleSame as aboveNo?
12
Inference11derivation-generation-use-inferencewasDerivedFrom->used, wasGeneratedBy?property chain or ruleJun: suggest as property chain in the owl. Khalid: in the definition of derivation wasDerivedFrom(id; e2, e1, a, g2, u1, attrs), the activity a is option, which means the the inference can only be made when a is specified.
13
Inference12revision-is-alternate-inferencewasRevisionOf->alternateOf?rule. Khalid: subPropery?Khalid: If that inference always holds, why dont we define alternateOf as a subproperty of wasRevisionOf? If so then we should raise this to the group.
14
Inference13attribution-inferencewasAttributedTo->wasGeneratedBy, wasAssociatedWith?property chain or ruleJun: suggest as property chain in the owl. Khalid: the attribution does not specify the activity whereby the entity was generated. So this inference can not be made in OWL.
15
Inference14delegation-inferenceactedOnBehalfOf->wasAssociatedWith?ruleJun: not sure how this can be properly implemented. Khalid: This inference can only be made when actedOnBahald specifies the activity, which is an optional attribute.
16
Inference15influence-inferenceYesprov-o.owlsubpropertyJun: to be raised to the group. Khalid: I agree with defining it as a sub-property.
17
Inference16alternate-reflexiveYesprov-constraints.owlreflexive
18
Inference17alternate-transitiveYesprov-constraints.owltransitive
19
Inference18alternate-symmetricYesprov-constraints.owlsymmetric
20
Inference19specialization-transitiveYesprov-constraints.owltransitive
21
Inference20specialization-alternate-inferenceYesprov-o.owlsubpropertyJun: to be raised to the group
22
Inference21specialization-attributes-inference?ruleJun: create a class Specialization as a subClass of Entity? Use specializationOf to define an existential quantification? Khalid: not sure this can be done simply by sub-classing. Sometimes the attributes can be heterogeneous, in the sense that they use different datatype/representation.
23
Inference22mention-specialization-inferenceYesprov-o.owlsubpropertyJun: to be raised to the group. Khalid: according to the OWL ontology mentionOf is a sub-property of specializationOf
24
Constraint23key-object?
25
Constraint24key-properties?
26
Constraint25unique-generationentity, wasGeneratedByYesprov-constraints.owlcardinality quantification on Entity class (max) and rules?see also inference 8. Khalid: Cant we simply define generation as functional?
27
Constraint26unique-invalidationentity, wasInvalidatedByYesprov-constraints.owlcardinality quantification on Entity class (max) and rules?see also inference 8. Khalid: the same as above
28
Constraint27unique-wasStartedByactivity, wasStartedByYesprov-constraints.owlcardinality quantification on Activity class (max) and rules?see also inference 9. Khalid: the same as above
29
Constraint28unique-wasEndedByactivity, wasEndedByYesprov-constraints.owlcardinality quantification on Activity class (max) and rules?see also inference 9. Khalid: the same as above
30
Constraint29unique-startTimeNorule?Khalid: define the property as functional?
31
Constraint30unique-endTimeNorule?Khalid: define the property as functional?
32
Constraint31unique-mention?I am not sure I agree with this constraint. Didn't review it because it was associated with a feature at risk
33
Constraint32start-precedes-endNoruleKhalid: OWL does not seems fit for expressing temporal relationship. so it is better to define them using other mechanisms.
34
Constraint33start-start-orderingNorule
35
Constraint34end-end-orderingNorule
36
Constraint35usage-within-activityNorule
37
Constraint36generation-within-activityNorule
38
Constraint37wasInformedBy-orderingNorule
39
Constraint38generation-precedes-invalidationNorule
40
Constraint39generation-precedes-usageNorule
41
Constraint40usage-precedes-invalidationNorule
42
Constraint41generation-generation-orderingNorule
43
Constraint42invalidation-invalidation-orderingNorule
44
Constraint43derivation-usage-generation-orderingNorule
45
Constraint44derivation-generation-generation-orderingNorule
46
Constraint45wasStartedBy-orderingNorule
47
Constraint46wasEndedBy-orderingNorule
48
Constraint47specialization-generation-orderingNorule
49
Constraint48specialization-invalidation-orderingNorule
50
Constraint49wasAssociatedWith-orderingNorule
51
Constraint50wasAttributedTo-orderingNorule
52
Constraint51actedOnBehalfOf-orderingNorule
53
Constraint52typingYesprov-constraints.owlowl reasoning (possibly)
54
Constraint53impossible-specialization-reflexiveYesprov-constraints.owlirreflexive
55
Constraint55impossible-property-overlapidentifiers of some properties cannot overlapNorule. Khalid: in OWL it is possible to define that two classes are disjoint. Is there any similar mechanism that we can use for properties?
56
Constraint56impossible-object-property-overlapidentifiers not overlappingNorule
57
Constraint57entity-activity-disjointYesprov-o.owl?disjoint classesDo we implement this in provo.owl?
58
Constraint58Membership-empty-collectionYesprov-constraints.owlcardinality quantification (min=0;max=0)I am not quite sure about this
59
60
Loading...
 
 
 
Sheet1