Copyright © 2014 Open Geospatial Consortium
54
10.1.2 Notation
Each UML model class equates to a data dictionary entity. Each UML model class attribute equates to a data dictionary element. The shaded rows define entities. The classes and
attributes within the data dictionary are defined by six attributes, described below. Besides, an seventh column provides additional information.
10.1.2.1 Name
A label assigned to a class or an attribute. The associations linking a class to another class are handled as roles. In this case, the Name of the role is that of the target class of the association.
Classes start with an upper case letter, with no spaces. Multiple words are concatenated, with each new subword starting with a capital letter example: XnnnYmmm. Class names are
unique within the entire data dictionary of this specification. Attribute names are unique within a class, not the entire data dictionary. Attribute names are made unique, within an
application, by the combination of the class and attribute names example: ResourceMetadata.title.
10.1.2.2 Definition
The class or attribute description.
10.1.2.3 ObligationCondition
This is a descriptor indicating whether a class or attribute shall always be documented in the registry or sometimes be documented i.e. contains values. This descriptor may have the
following values:
Mandatory M: The class or attribute SHALL be documented. Conditional C: Specifies an electronically manageable condition under which at least
one metadata entity or a metadata element is mandatory. ‘Conditional’ is used for one of the three following possibilities:
o Expressing a choice between two or more options. At least one option is
mandatory and must be documented. o
Documenting a class or an attribute if another element has been documented. o
Documenting an attribute if a specific value for another attribute has been documented.
To facilitate reading by humans, the specific value is used in plain text. If the answer to the condition is positive, then the class or the attribute shall be mandatory.
Optional O: The metadata entity or the metadata element may be documented or may not be documented. Optional classes may have mandatory elements; those elements
only become mandatory if the optional class is used.
Copyright © 2014 Open Geospatial Consortium
55
10.1.2.4 Maximum occurrence
Kategori