Difference between revisions of "Modeler:Tutorial/Integrity Checks"
From CaseTalk Wiki
m |
m |
||
| Line 1: | Line 1: | ||
Every fact type must have an intra UC. | = Every fact type must have an intra UC. = | ||
The N rule must be valid for every nominalized fact type. | =The N rule must be valid for every nominalized fact type.= | ||
The N-1 rule must be valid for every fact type. | =The N-1 rule must be valid for every fact type.= | ||
The subtype rule must be valid for every subtype. | =The subtype rule must be valid for every subtype.= | ||
The alias of an object/fact type must be unique. | =The alias of an object/fact type must be unique.= | ||
All object type expressions must be used. | =All object type expressions must be used.= | ||
Non-lexical object types without totality constraints must have a fact type expression. | =Non-lexical object types without totality constraints must have a fact type expression.= | ||
The actual population of every fact type must be verbalizable. | =The actual population of every fact type must be verbalizable.= | ||
A strict equality constraint must apply on each subtype tupel. | =A strict equality constraint must apply on each subtype tupel.= | ||
Fact types may not contain redundant role combinations. (2) | =Fact types may not contain redundant role combinations. (2)= | ||
The population should match the value constraints. | =The population should match the value constraints.= | ||
The population should match the totality constraints. | =The population should match the totality constraints.= | ||
Facts must have at least one sample population. | =Facts must have at least one sample population.= | ||
Roles must have distinct semantic meanings. | =Roles must have distinct semantic meanings.= | ||
Label types must contain a datatype definition. | =Label types must contain a datatype definition.= | ||
Fact types may not contain object types. (1) | =Fact types may not contain object types. (1)= | ||
Binary fact types must have grouping preference (1) | =Binary fact types must have grouping preference (1)= | ||
All generated expressions require validated semantics. | =All generated expressions require validated semantics.= | ||
Label types must be used. | =Label types must be used.= | ||
Populations must comply with uniqueness constraints | =Populations must comply with uniqueness constraints= | ||
Populations must comply with totality constraints (11) | =Populations must comply with totality constraints (11)= | ||
Population must comply with subset constraints | =Population must comply with subset constraints= | ||
Population must comply with datatype | =Population must comply with datatype= | ||
External expressions must be supported | =External expressions must be supported= | ||
External namespace must cover one version | =External namespace must cover one version= | ||
ValueConstraints must comply with datatype | =ValueConstraints must comply with datatype= | ||
Expression requires soft semantics | =Expression requires soft semantics= | ||
---- | ---- | ||