User:RailML Coord Documentation/Spielwiese: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 6: Line 6:


Further subschemas could potentially be developed according to the needs of the community.
Further subschemas could potentially be developed according to the needs of the community.
=== Interlocking (IL) ===
{{main|Interlocking}}
The [[interlocking|interlocking subschema]] will focus on information that infrastructure managers and signal manufacturing industry typically maintain in signal plans and route locking tables:
*Data transfer: a standard data exchange format will allow the automation of data transfer, which is the process of adapting a railway interlocking and signaling system to a specific yard.
*Simulation programs: the {{rml}} IL schema allows modelers to quickly absorb information about the interlocking systems such as timing behavior and routes and analyze the impact on railway capacity.
The subschema is developed with the participation of some European infrastructure managers and the signal manufacturing industry based on {{external|https://www.railtopomodel.org|RailTopoModel}}. A list of use cases for the {{rml}} interlocking schema can be found on page [[:Category:Use case (IL)]].

Revision as of 18:22, 20 November 2023

Current railML® subschemas

Currently, there are two subschemas available for productive use: Infrastructure (IS) and Interlocking (IL). The Timetable and Rostering (TT) and Rollingstock (RS) subschemas are in active development and can be obtained for development and test purposes. Elements that do not fit into this structure are subsumed in the class Common (CO).

Open https://www.railML.org/en/user/subschemes.html (external link) for a list of the current coordinators of the respective schemas and their contact data.

Further subschemas could potentially be developed according to the needs of the community.