Difference between revisions of "Modeler:Tutorial/Integrity Checks"
(Created page with " == Check 1 == Every fact type must have an intra UC. Message(s) The fact type has no intra UC. Type Error. == Check 2 == The N rule must be valid for every nominal...") |
m (Marcow moved page Modeler:Integrity Checks to Modeler:Tutorial/Integrity Checks without leaving a redirect) |
(No difference)
| |
Revision as of 05:24, 28 February 2013
Check 1
Every fact type must have an intra UC.
Message(s) The fact type has no intra UC.
Type Error.
Check 2
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.
Check 3
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.
Check 4
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.
Check 5
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.
Check 6
All object type expressions must be used.
Message(s) The object type expression is not used.
Type Warning.
Check 7
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.
Check 8
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.
Check 9
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.
Check 10
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.
Check 11
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.