Difference between revisions of "Main Page"

From wiki.railML.org
Jump to: navigation, search
[unchecked revision][unchecked revision]
m (FAQ: Link added to CO:fileConventions, Conventions for railML files)
m (FAQ)
Line 40: Line 40:
  
 
* [[IS:TrackConnections|Connection between tracks]]
 
* [[IS:TrackConnections|Connection between tracks]]
 +
* [[Diskussion:IS:mileageChange‎ | Remarks and open issues on mileage changes]]
  
 
=== Timetable and Rostering (TT) ===
 
=== Timetable and Rostering (TT) ===

Revision as of 18:29, 14 August 2015

Welcome to the railML Wiki / Willkommen im railML-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 and provides an open discussion platform.

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.

See our FAQ pages to see how to join the railML wiki and especially to contribute to this Wiki by editing element documentation sites or editing or creating FAQ sites.

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.

Auf unseren Hilfeseiten finden Sie Informationen zum registrieren für das railML-Wiki und insbesondere, wie Sie zum Wiki beitragen können durch das Ergänzen oder Verbessern der Elemente-Dokumentation oder durch das Erstellen oder Ergänzen von Hilfeseiten.

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.

Documentation

The following lists provide links to Infrastructure Documentation sites:

FAQ

Some general questions about infrastructure related aspects in railML files are summarized on the following wiki-sites:

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:

The following lists provide links to external Timetable Documentation sites from some railML partners:

FAQ

Some general questions about timetable related aspects in railML files are summarized on the following wiki-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
  1. vehicle as black box (with respect to dynamic characteristics) with only mean values
  2. vehicle as black box (with respect to dynamic characteristics) with curves for particular values being variable within the operating range
  3. 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.

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 Common Documentation sites:

FAQ

Some general questions about handling railML files are summerized on the following wiki-sites:

Developers Guides

railML subschema under development

Interlocking (IL)

The interlocking Schema is under active development from 2015.

Please visit the railML-Website for more detailed information about the Interlocking subschema or send an email to the coordinator of the subschema.

Documentation

The first attempt for documentation is provided at the railML IXL glossary.

An intended features list is stored in the Wiki.

All topics, that are covered by the current developments, will be removed from this features list and described at the glossary instead. Later on, the typical railML documentation with wiki sites for each element will be provided.

Proposed railML subschema

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).

Station asset management and properties

A schema for station databases, asset management and properties was developed in the early 2000's but place on hold due to the very limited use cases at this time. With a focus to the upcoming [PRM] a reopening of the development is planned for 2015.


Feel free to direct any comments, questions or remarks to the coordinators of railML.

Enjoy the Wiki!