Main Page
New to railML Wiki
Willkommen im RailML.org-Wiki
RailML® lebt von der Mitarbeit der Nutzer des Standards. Sie können an der Entwicklung teilhaben und Ihre Bedürfnisse und Erfahrungen in zukünftige railML®-Teilschemen einbringen. Unser Diskussionsforum steht Ihnen für allgemeine Fragen zum Projekt oder zu den einzelnen Teilschemen zur Verfügung.
Mit Hilfe dieses Wikis soll der Einstieg in die Entwicklung der railML®-Teilschemen erleichtert werden. Es ermöglicht den Benutzern neue Inhalte zu schaffen, sowie vorhandene Beiträge zu bearbeiten und damit eine umfassende Wissensdatenbank zum railML®-Standard aufzubauen.
Alle Einträge des Wikis sind in Englisch zu verfassen und gegebenenfalls mit deutschen Hinweisen zu ergänzen. Die Sprache der Benutzeroberfläche lässt sich nach dem Login anpassen.
Hilfe zur Benutzung des Wikis finden Sie im Benutzerhandbuch (externer Link zu einem anderen Wiki - nicht railML).
Welcome to the RailML.org Wiki
RailML® is not the finished development of a central group. Instead, railML® grows through the joint work of the partners and is steadily being extended. We invite you to participate on this future-oriented project and to take advantage of these standardized interfaces. Our Forum is meant to help coordinate the joint work of the development partners.
This wiki should supporting the development of railML ®-schemes. It allows users to create new content and edit existing articles, and setup a comprehensive knowledge database to the railML® standard.
All articles must be created in english. Additional German comments are allowed. The language of the user interface can be changed after login.
Please refer to the user manual (external link to a different wiki - not railML) for help to the wiki.
How to Join the Wiki
Joining the Wiki is very easy and only a matter of seconds.
- Go to the login page
- In the upper right corner of this page, you find a link to sign in to this Wiki. If you currently use the German layout of this Wiki, the link is called "Anmelden".
- Follow that link to get to the login page.
- Choose a user name and a password
- The first two text fields of the login page ask you to enter a user name and a password. The username can be arbitrary, but should be the first letter of your first name followed by a dot and your complete last name (like V.Knollmann for example).
- Since you are new to Wiki, you must re-enter you password, enter your email address and your real name. That what the lower three text fields are for.
- Now you can request a new account ("Neues Nutzerkonto anlegen") and are instantly able to work with the Wiki!
- Confirm your mail address
- Immediately after creating a new account, an email is sent to you which contains a link. Click that link to confirm that the mail address you've entered above is really yours.
- That's it!
- You are ready to contribute to the Wiki!
- If you like to, you can enter some information about you on your personal page. Your personal page's name is Benutzer:Username (like Benutzer:V.Knollmann).
How to start a new page
The easiest way to start a new page is to edit an existing page and insert a link to your new page there. Do this:
- Go to the page from which you want to link to your new page
- Click the "edit"- or "bearbeiten"-link (depending on the language you chose in the Preferences) the the page header
- Insert the link like this: Displayed Label in the text (just edit this page and look and the source to see how it works)
- Save the page (perhaps after previewing it) and click the new link you just inserted
- A new page pops up in which you can directly enter the contents of your new page
Current railML subschema
Infrastructure (IS)
General Information
The Infrastructure subschema contains a data structure for the storage of
- tracks, switches and the topology of a line
- various operations and control elements (e. g. signals along the track)
- tunnels, bridges
- any kind of "border" (owner change, gauge change, axle load change, electrification, ...)
- visualization data for displaying a net
Please visit the railML-Website for more detailed information about the Infrastructure subschema or send an email to the coordinator of the subschema.
There is also a "historic" collection of new features for the Infrastructer subschema. It was developed in the preparation works of railML version 1.1. Some of the suggestions are already implemented in the stable railML 2.0 release. Other extensions wait for users with strong needs for them.
Documentation
The following lists provide links to Infrastructure Documentation sites:
- Infrastructure Elements
- Infrastructure Types for Inheritance
- Infrastructure Attribute Groups
- Infrastructure Examples
Timetable and Rostering (TT)
General Information
The timetable subschema is part of the complete railML schema providing a data structure in XML language for the exchange of railway specific data.
The timetable schema provides container for all data about any kind of timetables for operational or conceptional purposes. A flexible description of operating periods, which are important elements while dealing with timetables, is also included in the schema.
The root element is always <railml>, thus it is even possible to combine data of timetable with those of other RailML schemas within one file. The main element for this schema is <timetable>, which is the root for data about any timetable.
With the new branch of <rosterings> it is intended to use this data schema as well for conceptional rolling stock schedules.
Please visit the railML-Website for more detailed information about the Timetable subschema or send an email to the coordinator of the subschema.
Documentation
The following lists provide links to Timetable Documentation sites:
Rollingstock (RS)
General Information
The rollingstock subschema is part of the complete railML schema providing a data structure in XML language for the exchange of railway specific data.
The rollingstock schema provides container for all data about any kind of rail vehicles including locomotives, multiple units, passenger and freight wagons. The second part of the schema enables the combination of single vehicles to formations as a fixed composition within a train or an entire train. The root element is always <railml>, thus it is even possible to combine data of rolling stock with those of other RailML schemes within one file. The main element for this schema is <rollingstock>, which is the root for data about any rolling stock.
It is intended to use this data schema for vehicle management as well as for detailed run-time calculations. Depending on the purpose only the <vehicles> branch of the data tree may be populated or the <formations> branch appears or both of them. The <vehicles> branch contains all data related to single vehicles. However, there are data, which are mainly used in relation to a composition of vehicles. Therefore the <formations> branch is used to reflect the characteristics an entire train or a composition of vehicles within a train.
The Rollingstock schema comprises the following features:
- separate parts for vehicles and for train parts or complete trains
- possible specification of vehicle families and individual vehicles using the common features of the family
- different level of detail for data
- vehicle as black box (with respect to dynamic characteristics) with only mean values
- vehicle as black box (with respect to dynamic characteristics) with curves for particular values being variable within the operating range
- vehicle as white box with details about the internal propulsion system
- vehicles with motive power, for passenger or freight use
- combination of vehicles to formations, i.e. train parts or complete trains
Please visit the railML-Website for more detailed information about the Rollingstock subschema or send an email to the coordinator of the subschema.
Documentation
The following lists provide links to Timetable Documentation sites:
Common (CO)
General Information
This subschema shall cover all topics, which affect all other railML-schemas alike.
Please visit the railML-Website for more detailed information about the Common subschema or send an email to the coordinator of the subschema.
The actual planned tasks and enhancements can be found at Trac-Tickets of the railML development space.
There is also a "historic" collection of proposed Data Types for the Common subschema. It was developed in the preparation works of railML version 1.1. Some of the suggestions are already implemented in the stable railML 2.0 release. Other extensions wait for users with strong needs for them.
Documentation
The following lists provide links to Timetable Documentation sites:
FAQ
Some general questions about handling railML files are summerized on the following wiki-sites:
- Local versus web-based validation (XML catalogs)
- Officially released versus developer version (Homepage, Subversion)
- Discussed versus agreed features (Newsgroup, Trac Tickets)
Proposed railML subschema
Interlocking (IL)
The Interlocking subschema shall store information about typical interlocking data like:
- train and shunting routes
- dependencies between signals, blocks and routes
- switches and derailers affected by a route
- overlappings
The Interlocking subschema doesn't exist yet but is currently being developed. The discussion related to the development is held in the infrastructure forum (or click here for access via HTTP). More static information like features lists is stored in the Wiki.
Shift planning
Additional to (vehicle) rosterings, there are ideas for implementing (personnel) shift planning.
It should be discussed in the timetable forum (or click here for access via HTTP).
Feel free to direct any comments, questions or remarks via email to the webmaster of railML.
Enjoy the Wiki!