Difference between revisions of "Modeler:Tutorial/Integrity Checks"
m |
m |
||
| Line 1: | Line 1: | ||
== | == Every fact type must have an intra UC == | ||
Every fact type must have an intra UC | |||
Message(s) | Message(s) | ||
| Line 12: | Line 10: | ||
== | == The N rule must be valid for every nominalized fact type == | ||
The N rule must be valid for every nominalized fact type | |||
Message(s) | Message(s) | ||
| Line 27: | Line 23: | ||
== | == The N-1 rule must be valid for every fact type == | ||
The N-1 rule must be valid for every fact type | |||
Message(s) | Message(s) | ||
| Line 38: | Line 32: | ||
== The subtype rule must be valid for every subtype == | |||
== | |||
The subtype rule must be valid for every subtype | |||
Message(s) | Message(s) | ||
| Line 50: | Line 41: | ||
== The alias of an object/fact type must be unique == | |||
== | |||
The alias of an object/fact type must be unique | |||
Message(s) | Message(s) | ||
| Line 63: | Line 51: | ||
== | == All object type expressions must be used == | ||
All object type expressions must be used | |||
Message(s) | Message(s) | ||
| Line 72: | Line 58: | ||
Type | Type | ||
Warning. | Warning. | ||
== | == 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 | |||
Message(s) | Message(s) | ||
| Line 90: | Line 73: | ||
== | == The actual population of every fact type must be verbalizable == | ||
The actual population of every fact type must be verbalizable | |||
Message(s) | Message(s) | ||
| Line 104: | Line 85: | ||
== A strict equality constraint must apply on each subtype tupel == | |||
== | |||
A strict equality constraint must apply on each subtype tupel | |||
Message(s) | Message(s) | ||
| Line 118: | Line 96: | ||
A strict equality constraint will be enforced on the tupels of common subtypes. | A strict equality constraint will be enforced on the tupels of common subtypes. | ||
== Fact types may not contain redundant role combinations == | |||
== | |||
Fact types may not contain redundant role combinations | |||
Message(s) | Message(s) | ||
| Line 135: | Line 108: | ||
== The population should match the Value Constraints == | |||
== | |||
The population should match the Value Constraints | |||
Message(s) | Message(s) | ||
Revision as of 09:39, 30 July 2018
Every fact type must have an intra UC
Message(s) The fact type has no intra UC.
Type Error.
The N rule must be valid for every nominalized fact type
Message(s) The N rule is not valid for . UC should cover all N roles. The N rule is not valid for . should contain all roles. (The fact type has no intra UC.)
Type Warning.
Remarks Most generalizations and common subtype violate this rule.
The N-1 rule must be valid for every fact type
Message(s) The N-1 rule is not valid for . (The fact type has no intra UC.)
Type Warning.
The subtype rule must be valid for every subtype
Message(s) Subtype role in should be covered by a narrow UC. Subtype role in should be played by a non-lexical object type. Subtype role in cannot be mandatory.
Type Error.
The alias of an object/fact type must be unique
Message(s) The alias of conflicts with the alias of . The alias of conflicts with the name of .
Type Error.
All object type expressions must be used
Message(s) The object type expression is not used.
Type Warning.
Non-lexical object types without totality constraints must have a fact type expression
Message(s) The population of might not be verbalizable.
Type Warning.
Remarks After the GLR process has been run tuples of the reported fact types might no longer be verbalizable.
The actual population of every fact type must be verbalizable
Message(s) The population of one or more object types / fact types should/will be corrected.
Type Warning, makes corrections.
Remarks If the checks finds tupels which cannot be verbalized, these tupels will be removed.
A strict equality constraint must apply on each subtype tupel
Message(s) The subtype has invalid tupels.
Type Error.
Remarks A strict equality constraint will be enforced on the tupels of common subtypes.
Fact types may not contain redundant role combinations
Message(s) ...
Type Warning.
Remarks Multiple facts are found which play the same combination of roles. Therefor these common roles may be objectified to reduce redundancy.
The population should match the Value Constraints
Message(s) ...
Type Warning.
Remarks The Value Constraint is checked on the sample population. It is an indication that either the sample is incorrect or the constraint is incomplete.