Symptom	Description	Properties
AmbiguousComponent	An inverse functional property maps two resources to the same resource. If the two resources are different, then this symptom signals an inconsistency.	The conflict property gives the conflicting facts, and the asserted property gives the inverse functionality constraint assertion.
CardinalityConstraint	A cardinality constraint was not satisfied. This includes max, min and equal cardinality constraints.	The cardinality constraint that was asserted is given by the constraint property. The property that is being constrained is given by property. The resource that is mapped to the wrong number of other resources is given by the instance property. The numerical relation (equality or inequality) that failed to hold is given by the unsatisfied property. Cardinality constraints are usually specified by asserting a subclass constraint between a class and a relation. This fact is given by the restriction property.
ConflictingFacts	Two facts conflict with one another. In other words, they cannot both hold and still be consistent. This is the superclass of several other symptom classes that specify more specific kinds of conflict.	The conflict property gives the conflicting facts. When there is an explicitly asserted statement that acts as a constraint (such as a functionality constraint on a property) then the assertion is given by the asserted property. The difference between the asserted fact and the conflicting facts is that the two conflicting facts are at the same "level" and are similar (such as two resources mapped to the same resource), while the asserted fact is on a different "level" (such as a functionality constraint). If the constraint is built-in then the asserted property will not have a value.
DisjointnessFailure	Two disjoint classes have an instance in common.	The conflict property gives the conflicting facts. When an explicit assertion of disjointness was made, then the asserted property gives this statement. Built-in disjointness constraints will not have a value for the asserted property.
FunctionalityFailure	A functional property maps a resource to two resources. If the two resources are different, then this symptom signals an inconsistency.	The conflict property gives the conflicting facts, and the asserted property gives the functionality constraint assertion.
IllegalStatement	A statement was asserted that is not allowed at the specified language level.	The asserted property gives the asserted illegal statement. Sometimes there will also be an item. This occurs when a list of a particular kind (given by the asserted property) contains an illegal element.
IncompleteUnion	A union or enumeration class has an instance that does not occur in the component classes (for a union) or is not one of the enumerators.	When there is an explicitly stated union or enumeration constraint, then it is given by the constraint property. Built-in constraints are not given. The instance of the union or enumeration is given by the asserted property (although it would seem that instance would be a better choice for this). For a union class, the instance should be an instance of one (or more) component classes. These facts may be given using the unasserted property. Similarly for enumeration classes.
LiteralConstraint	A literal was asserted to have a datatype with which its value is incompatible.	The asserted property gives the statement that the literal has the datatype.
MissingComponent	A required resource is missing. For example, rdf:first must always have exactly one value. This is a special case of a minimum cardinality constraint, but this symptom class is not a subclass of CardinalityConstraint.	The asserted property gives the statement which uses the resource in question. The unasserted property gives the statement which should have been asserted. The object of this statement does not exist, so shown as sym:unspecifiedEntity. However, this is just a placeholder. If two symptoms of this kind occur, the unspecified entities need not be the same.
MissingDeclaration	A resource was used in a manner that requires that it be an instance of particular class, but the resource was never explicitly declared to be such an instance. These symptoms are informational only, since the unasserted statement is immediately entailed. However, these symptoms are some of the most useful for catching errors. Spelling errors, for example, will result in a MissingDeclaration symptom.	The asserted property gives the statement which uses the resource in question. The unasserted property gives the statement which should have been asserted (although undeclared would be better).
MissingDeclaredValue	This is a combination of MissingComponent and MissingDeclaration. The value is not only missing, it also must be declared to be an instance of a particular class. This symptom arises from an owl:someValuesFrom constraint. This symptom is informational only because the necessary statements are entailed.	The owl:someValuesFrom constraint is specified using property, restriction and constraint as in the CardinalityConstraint symptom. The instance is given by the asserted property (although instance would be better). The missing value is given by unasserted as in MissingComponent, and the missing declaration is given by undeclared.
MissingItemDeclaration	An item in a collection is required to be an instance of a particular class, but it was not declared to be in this class. This is an informational symptom only because the declarations are entailed.	The asserted property gives the collection-valued statement that constrains the elements of the collection. The particular item that was not declared is given by the item property. The declaration that was not asserted is given by the unasserted property (although undeclared would have been better).
MissingValue	A particular case of an owl:hasValue constraint was not satisfied. This is informational only as the statement is entailed.	The owl:hasValue constraint is specified using property, restriction and constraint as in the CardinalityConstraint symptom. The instance is given by the instance property. The missing fact is given by unasserted property.
MissingValueDeclaration	A particular case of an owl:allValuesFrom constraint was not satisfied. This is informational only as the declaration is entailed.	The owl:allValuesFrom constraint is specified using property, restriction and constraint as in the CardinalityConstraint symptom. The instance is given by the instance property. The statement mapping the instance by the property to an undeclared value is given by the asserted property. The missing declaration is given by undeclared property.
TargetConstraint	Any of several constraints such as domain and range constraints that have exactly one asserted and exactly one unasserted statement. These are usually informational symptoms, but in some cases the symptom is an error when asserting the unasserted statement is not allowed.	The constraint (such as a domain constraint) is given by the constraint property. The statement (such as a mapping of a resource that does not satisfy the constraint) that gave rise to the constraint failure is given by the asserted property. The statement that should have been asserted is given by the unasserted property.