This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:designator> that might have replaced it. Do not hesitate to contact railML.org for further questions.
CO:designator: Difference between revisions
Jump to navigation
Jump to search
[unchecked revision] | [checked revision] |
(Created page with "{{subst:docBase |element=designator |subschema=CO}}") |
|||
Line 10: | Line 10: | ||
{{importComment}} | {{importComment}} | ||
=={{examples}}== | =={{examples}}== | ||
{{ | ===Usage of {{@|register}}=== | ||
In principle, {{@|register}} is defined as a {{xsdType|string}} and can be filled arbitrarily. Please, observe the rules explained under [[Dev:Registers#Expansion]]. In brief: | |||
* Registers that appear in [[dev:codelists|codelist]] [[registers.xml]] should be called by the respective code. E.g. ''register=DB640'' for the register of station codes of the Austrian Federal Railways (Dienstbehelf 640). | |||
* Registers that do not appear in ''registers.xml'' should be called with a project code starting with an underscore. E.g. ''register=_SnakeOilCatalogue''.<br>If the register you are referring to is widely employed, think about [[RailML3_Wiki:Contact|contacting us]] to get it included into the codelist. | |||
=={{Additional Information}}== | =={{Additional Information}}== | ||
==={{Notes}}=== | ==={{Notes}}=== | ||
==={{Open issues}}=== | ==={{Open issues}}=== |
Latest revision as of 17:49, 24 January 2022
Introduction
Documentation
Syntax
Changes 3.1→3.2
Removed with version 3.2. There exists an element <generic:designator> that might have replaced it.
Semantics
Best Practice / Examples
Usage of @register
In principle, @register is defined as a xs:string and can be filled arbitrarily. Please, observe the rules explained under Dev:Registers#Expansion. In brief:
- Registers that appear in codelist registers.xml should be called by the respective code. E.g. register=DB640 for the register of station codes of the Austrian Federal Railways (Dienstbehelf 640).
- Registers that do not appear in registers.xml should be called with a project code starting with an underscore. E.g. register=_SnakeOilCatalogue.
If the register you are referring to is widely employed, think about contacting us to get it included into the codelist.