components have some fields that have values represented by in specific parts of the hierarchy. These are referred to as concept enumerations.

The range of permitted values for each of the concept enumerations is the set of of a specified concept which is itself a subtype of . The current set of concept enumeration types is shown in . The values of each of these and the ways they should be used in implemented systems are described in the following subsections.


Core metadata concept (core metadata concept) (900000000000442005)


Concept

Comment

Each subtype of this concept represents a development module. These concepts provide values to the field that is present in all component release files. The value indicates the module within which a was created and is being maintained.

Each subtype of this concept represents a value that can be applied to the concept. field. This is used to indicate whether the current set of defining applied to a concept are sufficient to define it relative to its supertypes.

Each subtype of this concept represents a value that can be applied to the description. field. This is used to indicate whether the description represents a , a , a text definition or some other symbolic or textual representation of the associated concept.

Each subtype of this concept represents a value that can be applied to the description. field. This is used to indicate whether the text of the term can be modified to by switching characters from upper to lower case (or vice-versa).

Each subtype of this concept represents a value that can be applied to the relationship. field. This is used to indicate whether a relationship forms part of the definition of the source concept.

Each subtype of this concept represents a value that can be applied to the relationship. field. This is used to indicate the type of (DL) restriction (some, all, etc.) that applies to the relationship.

Each subtype of this concept represents a value that can be applied to the identifier. field. This is used to indicate the scheme to which the identifier value belongs.

Note: Many of the concept enumerations include values that significantly impact the meaning or use of a component. Therefore, implementers may find it necessary to partially hard-code the way their systems process particular values. In these cases, the concept referenced by the value is only of value when there is a requirement to display a human readable rending of the value. The main exceptions to this are and both of which represent extensible sets of values as new modules or alternative identifier schemes may be added in local .