Railway Markup Language
Sign in to saveAlso known as railML, Railml, RailML, .railml, .railmlx
railML (Railway Markup Language) is a proprietary freeware XML Schema-based data exchange format for data interoperability of railway applications.
Key facts
- File format.name
- Railway Markup Language
- File format.icon
- file:RailML_headr.png
- File format.iconcaption
- Logo of railML file format
- File format.icon_size
- 200px
- File format.extensions
- .railml, .railmlx
- File format.owner
- railML.org
- File format.developer
- railML.org; Dresden / Germany
- File format.latest release version
- 3.3
- File format.genre
- Railway exchange format
- File format.extended from
- XML
- File format.standards
- Industry standardISO/TS 4398:2022
- File format.open
- No, CC BY-NC-ND with additional restrictions
- File format.free
- Yes
- File format.url
- www.railml.org
via Wikipedia infobox
Wikidata facts
- Genre
- markup language
- Based on
- XML
- Official website
- www.railML.org
Show 5 more facts
- file extension
- railml
- media type
- application/zip
- publication date
- 2005-12-22
- described at URL
- www.railml.org/schemas/2018
- XML namespace URL
- www.railml.org/schemas/3.1
via Wikidata · CC0
~13 min read
Encyclopedic overview
21 sectionsContents
- Motivation
- Outline
- History
- Working principle
- Licensing and pricing
- Legal entity
- railML schemas
- Timetable
- Infrastructure
- Rolling stock
- Interlocking
- Code example
- Versions
- Usage of railML data
- Computer programmes
- railVIVID
- railML.org initiative
- Members
- Cooperations
- References
- External links
railML (Railway Markup Language) is a proprietary freeware XML Schema-based data exchange format for data interoperability of railway applications.
==Motivation== thumb|Advantage of a universal exchange format The growing number of computer applications modeling different aspects of railway operations, with different operators developing separate solutions parallelly, bore a chronic difficulty of connecting different railway IT applications. The exchange of data for operation concepts, slot management, simulation or infrastructure planning, etc. was possible either by hand or with a lot of special developed interfaces with loss of time and cost problems for railway companies. If there are n applications that are supposed to exchange data, with a special interface for each pair of programs respectively, \frac{n\cdot(n-1)}{2} interfaces are required—only one, if n=2, but 10, if n=5—increasing the complexity above average.
Excerpted from Wikipedia’s “Railway Markup Language” article, available under the CC BY-SA 4.0 licence.