Search results

Codelist Registers The file Registers.xml contains a list of railway related registers, databases, handbooks etc. The items are named <register> with the

constraint(s)! register: Name of the register, e.g. registers for OCPs: IBNR, DB640, RL100 or DIDOK. Choose a value from the railML® codelist Registers.xml or

practical usage. Example: <register code="_CRL"> ... </register> Ziel der vorgenannten, koordinierten Sammlung der Register ist es, eine eindeutige Zuordnung der

<additionalName> description, name, rail:lang, xsi:type <designator> endDate, entry, register, startDate <vehicleManufacturer> code, description, id, name, rail:lang

diff --git a/schema/Registers.xml b/schema/Registers.xml deleted file mode 100644 index ad61cc8..0000000 --- a/schema/Registers.xml +++ /dev/null @@ -1

topology register and can interpret the version(s)/variant(s). If the validity periods are not uniquely defined by the specifications register and entry

codelists/InfrastructureManagers.xsd codelists/ListBaseTypes.xsd codelists/Registers.xml codelists/Registers.xsd codelists/TrainProtectionSystems.xml codelists/TrainProtectionSystems

exports from tools which are certified by railML.org commitee. Being a registered trademark, railML® should be a kind of quality sign. As a certification

codelist All New users Concept Dev:Registers The codelist Registers contains registers, databases, handbooks etc. CO New users Concept Dev:TrainClearanceGauges

country="80"/> <designator register='RL100' entry='NPA'/> <designator register='ENEE' entry='80-26506-6'/> <designator register='PLC' entry='DE18274'/> <designator

diff --git a/schema/Registers.xml b/schema/Registers.xml new file mode 100644 index 0000000..ad61cc8 --- /dev/null +++ b/schema/Registers.xml @@ -0,0 +1,29

<xs:attribute name="register" type="xs:string" use="required"> + <xs:annotation> + <xs:documentation>name of the register, e.g. registers for OCPs: IBNR, DB640