|
|
| Line 1: |
Line 1: |
| = Every fact type must have an intra UC = | | = Every fact type must have an intra UC = |
| Object Types and Fact types contain roles. There must at least exist a uniqueness constraint.
| | 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.= | | =The N rule must be valid for every nominalized fact type.= |
Revision as of 09:50, 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.
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