Dev:Registers

This page is under construction. Sorry for temporary problems. See the discussion page to find a summary of the tasks and to coordinate the work on this page. Recognize that the content of this page may change quickly. Ferri Leberl (talk) 15:04, 9 January 2018 (CET)

The codelist Registers contains registers, databases, handbooks etc. Your railML^® download will usually contain the codelist in a directory codelists, next to documentation and schema. As As the codelists have shorter cycles than railML® versions have you might want to get the current list from https://svn.railml.org/railML2/trunk/codelists/Registers.xml.

The code lists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity errors. Moreover, the separation of schema and codelists allows actualizing the codelists in very short cycles. The concept of codelists is explained here.

Missing entries

Are you missing an entry? Did you find a mistake? We try to serve you with current, comprehensive and correct codelists and will try to add necessary entries as soon as possible. The actualization of the codelists does not follow the usual railML^® actualization cycles but happens in short terms.

• Inform the railML^® coordinator about a missing, incomplete or faulty entry — see https://www.railml.org/en/user/subschemes.html for the contact data.
• The coordinator will check your supplements and, where appropriate, include them into the regarding code list.
• The actualized codelist will be published in the SVN under https://svn.railml.org/railML2/trunk/codelists.

Current codelists

The current codelists are:

InfrastructureManagers

The list contains infrastructure managing companies. The items are named <infrastructureManager> with the following specification:

• Attributes
  • code: a code, that should be referred to from within an railML file, typically a short name for the infrastructure manager in latin letters. It links the railML^® element <infrastructureManager> with the code list.
• Children
  • <name>: The company name, with attribute
  • <isoCountryCode>: The two-digit country code of the company according to ISO 3166-1 alpha-2.
  • <companyCode>: Company codes according TAF TAP TSI B.8 or UIC IRS/leaflet 920-1:2006.

For an example entry see #Concept.

Structure

The items are named <register> with the following specification:

• Attributes
  • code: A code, that should be referred to from within an railML^® file
• Children
  • <name>: Internationalized name of the operation or control point register
  • <organization>: Organization name that is responsible for the register
  • <remarks>: Internationalized remarks for the operation or control point register

Example entry

<register code="RL100">
 <name xml:lang="de-DE">Betriebsstellenverzeichnis</name>
 <organization xml:lang="de-DE">DB</organization>
 <remarks xml:lang="de-DE">auch/früher als DS100 oder Ril100 bezeichnet</remarks>
 <remarks xml:lang="en">also/former known as DS100 or Ril100</remarks>
</register>

Affected Elements

Currently the codelist InfrastructureManagers.XML can be called from three elements:

In this article there is information missing with respect to the elements calling this codelist. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion page. Ferri Leberl (talk) 18:19, 9 January 2018 (CET)

Current entries

As of January 2018, the following companies are listed:

railML® Code	Name	Organization	Remarks	Scope	URL	Contact

Are you missing an entry? The procedure to extend the list is explained here.