The file serializes values for the opposite of a property declared composite. Details

A cycle exists in the uml:OwnedElement property of the reported elements. Details

The xmi:type attribute was specified with an XML element that uses href. Details

Major errors: It is unlikely that a processor will function when faced with these.
(The valiadator will report the error and stop.):

An error that is not classified. See the error text for details.

Either an XMI namespace was not provided or what was provided is not known to be associated with XMI.

No uml:Model element can be found in the XMI file.

XML errors.

Validator Limitations: These are things that are not problems with the
exchange file, but rather current limitations of the validation tool. The
Validator sometimes sets properties in the model to an enumeration value
'TOOL-LIMITATION' to express the occurrence of the limitation. Instances of these
are reported too.

None noted at this time.

Additional notes about the Validator

Here are some things to keep in mind when using the Validator:

Objects are represented as:

< 'className' 'instanceName', id='someNumber'> if it is a NamedElement with a name;

< 'className' <<'stereotypeName'>> 'instanceName', id='someNumber'>
if it is stereotyped object with a name;

< 'className' [unnamed], id='someNumber'> if it is an unnamed NamedElement, and;

< 'className' id='someNumber'> otherwise.

The 'id' has no meaning outside of the Validator.

Enumerations are represented as the enumeration value preceded by a '#'.

Collections are represented by < Set|Bag|Sequence|OrderedSet of 'elementCount' 'type' >

The value of a Collection is represented by ['value' , 'value'....].

Unset values are represented by 'null'

The errors are listed in an order suggested for their resolution
(resolve the earlier ones first). The reason we suggest this ordering
is that some of the earlier errors have repercusions (they produce subsequent errors).
There is little point in investigating a 'missing mandatory' value error,
for example, when the source of the error is reported more specifically
as use of an xmi:idref where the referent is not in the file.

When the Model attempts to define a Set, but the members supplied
contain duplicates, the Validator reports the error and creates a Bag
with all the members. Using a Bag might have repercusions in later
processing, but removing the duplicates and creating a Set is
simplistic and can also lead to downstream problems. Note: The error
message, but not the Model, describes the object as a Set. The corresponding
Bag in the Model has an id one greater than the offending Set object
reported in the error message.

Validator results are available for 30 minutes after the file is run.
After 30 minutes, the information associated with the run (information
attached to the session cookie) is garbage collected.
If 30 minutes seems too short, let me know.

Model Diff

The Model Diff capability is used to compar an uploaded user model of a MIWG test case
against a reference model of that test case. It reports where one of the two models
has an element that the other does not, and where values of properties of elements
differ.

Models Pre-loaded into the Validator

The models listed below are loaded into the Validator and can be referenced as a whole
through the 'XML namespace URI' shown. Elements of the model can be referenced through
the 'XMI href URI' shown.