Overview of naming conventions
The Dutch Taxonomy consists of various components that have to be named. Obviously the most important are the thousands of concepts, but in addition to a name, concepts also need a (presentation) label and a file in which they are defined and therefore there are more components that are needed to make the Dutch Taxonomy technically viable and usable from a functional point of view. In this part of the Dutch Taxonomy Architecture, for each of those components rules are laid down in relation to the naming. This is necessary because there are several parties who will create concepts, labels, etc. This is to ensure consistent naming of these components, to avoid confusion about components that are similarly named but with different meanings and to improve the comparability and traceability across all components together. If implementation of the name rules are fulfilled to the letter, it has to be possible to quickly localise potential duplication. Ultimately, the author of a component is personally responsible for providing a consistent name.
Overview of the naming guidelines
- 3.02 Naming - Total
- 3.02.01 Files and directories
- 3.02.02 Dutch Taxonomy Partners
- 3.02.03 Namespace URI
- 3.02.04 Namespace prefix
- 3.02.05 Element @name
- 3.02.06 Element @id
- 3.02.07 Element Standard Label
- 3.02.08 Element type @name
- 3.02.09 Linkrole URI
- 3.02.10 Linkrole @id
- 3.02.11 @xlink:label (according to locator and resource)
- 3.02.12 link:part @name
- 3.02.13 Enumeration values
- 3.02.14 Context elements
- 3.02.15 Language aspects
- 3.02.16 @id (according to resource)
- 3.02.17 @id (according to enumeration values)
- The exact description of an element HAS to be included in a documentation label or in references (that does not mean that they HAVE to be present).
- The standard label is not documentation or a clarification.