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

Revision as of 09:45, 30 July 2018

Every fact type must have an intra UC.

The N rule must be valid for every nominalized fact type.

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

The subtype rule must be valid for every subtype.

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.

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

@@ 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.
-Message(s)
-The fact type has no intra UC.
-Type
-Error.
-== The N rule must be valid for every nominalized fact type ==
+The N-1 rule must be valid for every 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 ==
+The subtype rule must be valid for every subtype.
-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 ==
+The alias of an object/fact type must be unique.
-Message(s)
-The object type expression is not used.
-Type
-Warning.
-== Non-lexical object types without totality constraints must have a fact type expression ==
+All object type expressions must be used.
-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 ==
+Non-lexical object types without totality constraints must have a fact type expression.
-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 ==
+The actual population of every fact type must be verbalizable.
-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.
+A strict equality constraint must apply on each subtype tupel.
-== The population should match the Value Constraints ==
+Fact types may not contain redundant role combinations. (2)
-Message(s)
-...
+The population should match the value constraints.
-Type
+The population should match the totality constraints.
-Warning.
+Facts must have at least one sample population.
-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.
+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
 ----