Check ID
This component has no identifier (yet)!
Check successor
There can only be a successor component/profile if the status of this component/profile is deprecated!
Cardinality root component
The minimum cardinality of the root component should be 1!
The maximum cardinality of the root component should be 1!
At the root level there should always be a Component.
Check for empty components
Component[] is empty (according to the ISO 24622-1:2015 Component Metadata model), i.e., contains no component or element!
Component[] is empty, i.e., contains no component, element or attribute!
Check siblings
Sibling components or elements should all have a different name. Found multiple components or elements named ''!
Check component siblings
Sibling components should all be different. Found multiple components with ID ''!
Some information an application (eg Arbil) can display to give guidance to the user when entering metadata.
Check Documentation siblings
Sibling Documentation elements should all be for different languages. Found multiple Documentation elements with xml:lang ''!
Check Element ValueScheme
An Element must have either a @ValueScheme or a ./ValueScheme!
The AttributeList child of an element contains a set of XML attributes for that element.
When an element is linked to a regular expression or a controlled vocabulary, the ValueScheme sub-element contains more information about this.
Check Vocabulary URI
When an external vocabulary is used (identified by the @URI) a @ValueProperty has to be specified!
Specification of a regular expression the element should comply with.
Specification of an open or closed vocabulary
A list of the allowed values of a controlled vocabulary.
Check Attribute ValueScheme
An Attribute must have either a @ValueScheme or a ./ValueScheme!
Check reserved attribute names
Attributes with name 'ref' or 'ComponentId' will not be available in a downgrade to CMDI 1.1!
Check attribute siblings
All attributes in an attribute list should have a different name. Found multiple attributes named ''!
For the use of a regular expression or a controlled vocabulary as the type of the attribute.
The name of the attribute.
A link to the ISOcat data category registry (or any other concept registry).
For the use of simple XML types as the type of the attribute.
Is the attribute required or not?
The name of the element.
A link to the ISOcat data category registry (or any other concept registry).
Used to specify that an element has a simple XML type (string, integer, etc)
Minimal number of occurrences.
Maximal number of occurrences.
Indicates that this element can have values in multiple languages (and thus is repeatable). This will result in the possibility of using the xml:lang attribute in the metadata instances that are created.
Check component attributes
A Component should have a name or a ComponentRef!
Check component reference
A root Component of a non-profile specification should not have a ComponentRef!
Indicates that a component (using its unique Header/ID issued by the ComponentRegistry) should be included.
A link to the ISOcat data category registry (or any other concept registry). Currently not used.
cardinality for elements and components
Check cardinalities
Maximum cardinality (0) cannot be lower than the default minimum cardinality (1)!
Minimum cardinality () should be lower or equal then the default maximum cardinality (1)!
Minimum cardinality () should be lower or equal then the maximum cardinality ()!
Minimum cardinality (unbounded) can't be higher than the (default) maximum cardinality ()!
Subset of XSD types that are allowed as CMD type
controlled vocabularies
End-user guidance about the value of the controlled vocabulary as a whole. Currently not used.
An item from a controlled vocabulary.
CMD enumeration item
All items in an enumeration should be different. Found multiple items with value ''!
A link to the ISOcat data category registry (or any other concept registry) related to this controllec vocabulary item.
End-user guidance about the value of this controlled vocabulary item.