Difference between revisions of "Modeler:Tutorial/Integrity Checks"

From CaseTalk Wiki
Jump to: navigation, search
Line 8: Line 8:
If a fact type with n roles has at least one uniqueness constraint on less than n-1 roles, then the fact type is splittable. The n-1 rule-test simply consists of the check that there are no UCs that are too small.
If a fact type with n roles has at least one uniqueness constraint on less than n-1 roles, then the fact type is splittable. The n-1 rule-test simply consists of the check that there are no UCs that are too small.


=The subtype rule must be valid for every subtype.=
= The subtype rule must be valid for every subtype =
- There can be no single role totality constraint on the role of a unary fact type.


=The alias of an object/fact type must be unique.=
=The alias of an object/fact type must be unique.=

Revision as of 09:57, 30 July 2018

Every fact type must have an intra UC

For each fact type, there must be at least one uniqueness constraint that concerns one or more roles of this fact type only.

The N rule must be valid for every nominalized fact type

Every nominalized fact type with n roles only has exactly one uniqueness constraint over all n roles.

The N-1 rule must be valid for every fact type

If a fact type with n roles has at least one uniqueness constraint on less than n-1 roles, then the fact type is splittable. The n-1 rule-test simply consists of the check that there are no UCs that are too small.

The subtype rule must be valid for every subtype

- There can be no single role totality constraint on the role of a unary fact type.

The alias of an object/fact type must be unique.

All object type expressions must be used.

Non-lexical object types without totality constraints must have a fact type expression

If no totality constraint at all applies to any of the roles played by a certain nominalized fact type, then that fact type must have an existence postulating fact type expression.

The actual population of every fact type must be verbalizable.

A strict equality constraint must apply on each subtype tupel.

Fact types may not contain redundant role combinations. (2)

The population should match the value constraints.

The population should match the totality constraints.

Facts must have at least one sample population.

Roles must have distinct semantic meanings.

Label types must contain a datatype definition.

Fact types may not contain object types. (1)

Binary fact types must have grouping preference (1)

All generated expressions require validated semantics.

Label types must be used.

Populations must comply with uniqueness constraints

Populations must comply with totality constraints (11)

Population must comply with subset constraints

Population must comply with datatype

External expressions must be supported

External namespace must cover one version

ValueConstraints must comply with datatype

Expression requires soft semantics


Back: Subtype and Generalisation