MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"query": {
"normalized": [
{
"from": "Main_Page",
"to": "Main Page"
}
],
"pages": {
"1": {
"pageid": 1,
"ns": 0,
"title": "Main Page",
"cirrusdoc": [
{
"index": "k156663_wiki3_135_content_first",
"type": "_doc",
"id": "1",
"version": [],
"source": {
"version": 8942,
"wiki": "k156663_wiki3_135",
"namespace": 0,
"namespace_text": "",
"title": "Main Page",
"timestamp": "2024-05-02T08:56:57Z",
"create_timestamp": "2019-09-05T16:04:00Z",
"category": [
"External Link"
],
"external_link": [
"https://development.railml.org/railml/version3/-/commit/a881cdcfa4dcc1a6de061b304d17147dfd688b7f",
"https://railML.org",
"https://www.railML.org",
"https://en.wikipedia.org/wiki/RailML",
"https://wiki2.railml.org",
"https://de.wikipedia.org/wiki/railML",
"https://www.railML.org/en/user/subschemes.html",
"https://www.railtopomodel.org",
"https://development.railml.org/railml/version2/-/issues/",
"https://development.railml.org/railml/version3/-/issues/",
"https://en.wikipedia.org/wiki/Loading_gauge",
"https://www.railml.org/en/developer/version-timeline.html",
"https://development.railml.org/railml/version3",
"https://www.railml.org/en/user/licence.html"
],
"outgoing_link": [
"Common",
"Dev:Codelists",
"Dev:How_to_join,_edit_and_create_the_railML_wiki",
"Dev:Special_Wiki_Markup",
"Dev:UML",
"Dev:Wiki_Documentation_Guidelines",
"Dev:XMLtree",
"Dev:changes",
"IS:topology",
"Infrastructure",
"Interlocking",
"Rollingstock",
"Timetable",
"UC:Use_cases",
"RailML3_Wiki:Statistics",
"Category:Use_case_(IL)",
"Category:Use_case_(IS)",
"Category:Use_case_(TT)"
],
"template": [
"Template:Navi",
"Template:External",
"Template:Rml",
"Template:Deu",
"Template:Wiki2",
"Template:Main",
"Template:Ticket",
"Template:Current",
"Template:Site",
"Template:Commit"
],
"text": "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. \u2192Main Article: Interlocking The 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 railML\u00ae 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 RailTopoModel (external link). A list of use cases for the railML\u00ae interlocking schema can be found on page Category:Use case (IL). \u2192Main Article: Infrastructure The railML\u00ae Infrastructure subschema is focused on the description of the railway network infrastructure including all its various facets that are needed by the data exchange applications. In particular, the railML\u00ae infrastructure schema contains the following information: Topology: The track network is described as a topological node edge model, partly explained by the Simple example. Coordinates: All railway infrastructure elements can be located in an arbitrary 2- or 3-dimensional coordinate system, e.g. the WGS84 that is widely used by today's navigation software. Geometry: The track geometry can be described in terms of radius and gradient. Railway infrastructure elements: They enclose a variety of railway relevant assets that can be found on, under, over or next to the railway track, e.g. balises, platform edges, and level crossings. Further located elements encompass elements that are closely linked with the railway infrastructure, but that \"cannot be touched\", e.g. speed profiles and track conditions. A list of use cases for the railML\u00ae infrastructure schema can be found on page Category:Use case (IS). \u2192Main Article: Rollingstock The rollingstock subschema is part of the complete railML\u00ae schema providing a data structure in XML language for the exchange of railway specific data. The rollingstock schema provides a container for all data about any kind of rail vehicle 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. It is intended to use this data schema for vehicle management as well as for detailed run-time calculations. 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 vehicles as black boxes (with respect to dynamic characteristics) with only mean values vehicles as black boxes (with respect to dynamic characteristics) with curves for particular values being variable within the operating range vehicles as white boxes 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 \u2192Main Article: Timetable and Rostering The timetable subschema is part of the complete railML\u00ae schema providing a data structure in XML for the exchange of railway specific data. It is the subschema that is most widely used. The timetable subschema is used for all data necessary to exchange any kind of timetable for operational or conceptional purposes including the following information: Operating Periods: The operating days for train services or rostering. Train Parts: The basic parts of a train with the same characteristics such as formation and operating period. The train part includes the actual information regarding the path of the train as a sequence of operation or control points together with the corresponding schedule information. Trains: One or more train parts make up a train and represent either the operational or the commercial view of the train run. Connections: The relevant connections/associations between trains at a particular operation or control point. Rostering: Train parts can be linked to form the circulations necessary for rostering (rolling stock schedules). A list of use cases for the railML\u00ae timetable schema can be found on page Category:Use case (TT). \u2192Main Article: Common The Common class shall cover all topics, which affect all other railML-schemas alike. The actual planned tasks and enhancements can be found in the railML\u00ae 2 ticket system and the railML\u00ae 3 ticket system respectively. Please note that 2023-04-24 Common was split into Common and Generic due to technical reasons \u2192Main Article: Codelists Certain attributes require a choice from a vast, highly standardized but shifting set of values. For instance, there are many regional clearance gauge standards (external link). As to facilitate the usage and update of the sets, this Information is outsourced into codelists outside the railML\u00ae schema. The codelists are identically available for railML\u00ae 2 and railML\u00ae 3. The current railML\u00ae 3 version is 3.2. For railML\u00ae 2 see here. For more details see our version timeline (link to the railML\u00ae website). The development of railML\u00ae 3 can be tracked on https://development.railml.org/railml/version3 (link to the railML\u00ae website). railML\u00ae is licensed dually under a restricted form of the Creative Commons License CC-BY-NC-ND and a commercial license. An overview of the regarding licenses can be found under https://www.railml.org/en/user/licence.html (link to the railML\u00ae website). How to join, edit and create the railML wiki Wiki Documentation Guidelines Special Wiki Markup Statistics Feel free to direct any comments, questions or remarks to the coordinators of railML\u00ae. For our contact information see Contact [a881cdcfa4dcc1a6de061b304d17147dfd688b7f] Enjoy the Wiki!",
"source_text": "\n{{navi}}\n=== Welcome to the {{rml|3}} wiki / {{Deu| Willkommen im {{rml|3}}-Wiki}}===\n{| class=\"wikitable toptextcells\" style=\"text-align:left vertical-align:top\"\n|- style=\"vertical-align:top;\"\n|style=\"width:45%\" | {{rml}} ('''rail'''way '''M'''arkup '''L'''anguage) is an open, XML based data exchange format for data interoperability of railway applications. For further information please visit the [https://www.railML.org official project website] or [https://en.wikipedia.org/wiki/RailML Wikipedia].\n\nThis wiki is dedicated to all Versions of {{rml|3}}. A separate wiki for {{rml|2}} is available {{wiki2|2=here}}. This wiki should support you in the development of {{rml|3}} interfaces and inform you about the basic elements and modelling concepts of the {{rml|3}} schema.\n\nYou are invited to contribute to this wiki and to the development of the {{rml}} schema. Please, see our guideline \"''[[dev:How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|How to join the railML wiki]]''\" to get to know the standards of railML's wiki and the procedure for getting a writer's account. You can find further guidelines on {{rml}} in section [[#Users_and_Developers_Guides]].\n\nThis wiki is currently being kept only in English.\n|style=\"width:*\" | {{Deu|{{rml}} ('''rail'''way '''M'''arkup '''L'''anguage) ist ein offenes, XML-basiertes Datenaustauschformat zur gegenseitigen Ben\u00fctzbarkeit der Daten von Anwendungen im Eisenbahnbereich. F\u00fcr weitere Informationen besuchen Sie bitte die [https://www.railML.org offizielle Projektwebsite] oder [https://de.wikipedia.org/wiki/railML Wikipedia].}}\n\n{{Deu|Dieses Wiki ist s\u00e4mtlichen Versionen von {{rml|3}} gewidmet. Ein separates wiki f\u00fcr {{rml|2}} finden Sie {{wiki2|hier}}. Ziel dieses Wikis ist, Sie bei der Entwicklung von {{rml|3}}-Schnittstellen zu unterst\u00fctzen und Sie \u00fcber die grundlegenden Elemente und Modellierungskonzepte des {{rml|3}}-Schemas zu informieren.}}\n\n{{Deu|Sie sind herzlich eingeladen, sich an der Entwicklung dieses Wikis sowie des {{rml}}-Schemas zu beteiligen. Lesen Sie dazu bitte unseren Leitfaden ''\u201e[[dev:How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|How to join the {{rml}} wiki]]\u201c'', um sich mit den Standards des {{rml}}-Wikis vertraut zu machen und die Vorgangsweise zur Erteilung eines Autorenaccounts kennenzulernen. Weitere Leitf\u00e4den, die {{rml}} betreffen, finden Sie im Abschnitt [[#Users_and_Developers_Guides]].}}\n\n{{Deu|Dieses Wiki wird derzeit ausschlie\u00dflich auf}} Englisch {{Deu|gef\u00fchrt.}}\n|}\n\n== Current {{rml}} subschemas ==\n\nCurrently, 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).\n\nOpen {{external|https://www.railML.org/en/user/subschemes.html}} for a list of the current coordinators of the respective schemas and their contact data.\n\nFurther subschemas could potentially be developed according to the needs of the community.\n=== Interlocking (IL) ===\n{{main|Interlocking}}\nThe [[interlocking|interlocking subschema]] will focus on information that infrastructure managers and signal manufacturing industry typically maintain in signal plans and route locking tables:\n*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.\n*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.\n\nThe 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)]].\n\n=== Infrastructure (IS) ===\n{{main|Infrastructure}}\nThe {{rml}} [[Infrastructure|Infrastructure subschema]] is focused on the description of the railway network infrastructure including all its various facets that are needed by the data exchange applications. In particular, the {{rml}} infrastructure schema contains the following information:\n* [[IS:topology|Topology]]: The track network is described as a topological node edge model, partly explained by the '''[[IS:topology|Simple example]]'''.\n* Coordinates: All railway infrastructure elements can be located in an arbitrary 2- or 3-dimensional coordinate system, e.g. the WGS84 that is widely used by today's navigation software.\n* Geometry: The track geometry can be described in terms of radius and gradient.\n* Railway infrastructure elements: They enclose a variety of railway relevant assets that can be found on, under, over or next to the railway track, e.g. balises, platform edges, and level crossings.\n* Further located elements encompass elements that are closely linked with the railway infrastructure, but that \"cannot be touched\", e.g. speed profiles and track conditions.\nA list of use cases for the {{rml}} infrastructure schema can be found on page [[:Category:Use case (IS)]].\n\n=== Rollingstock (RS) ===\n{{main|Rollingstock}}\nThe [[rollingstock|rollingstock subschema]] is part of the complete {{rml}} schema providing a data structure in XML language for the exchange of railway specific data.\n\nThe rollingstock schema provides a container for all data about any kind of rail vehicle 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. It is intended to use this data schema for vehicle management as well as for detailed run-time calculations.\n\nThe Rollingstock schema comprises the following features:\n\n* separate parts for vehicles and for train parts or complete trains\n* possible specification of vehicle families and individual vehicles using the common features of the family\n* different level of detail for data\n:# vehicles as black boxes (with respect to dynamic characteristics) with only mean values\n:# vehicles as black boxes (with respect to dynamic characteristics) with curves for particular values being variable within the operating range\n:# vehicles as white boxes with details about the internal propulsion system\n* vehicles with motive power, for passenger or freight use\n* combination of vehicles to formations, i.e. train parts or complete trains\n\n=== Timetable and Rostering (TT) ===\n{{main|Timetable|Timetable and Rostering}}\nThe [[timetable|timetable subschema]] is part of the complete {{rml}} schema providing a data structure in XML for the exchange of railway specific data. It is the subschema that is most widely used.\n\nThe timetable subschema is used for all data necessary to exchange any kind of timetable for operational or conceptional purposes including the following information:\n* Operating Periods: The operating days for train services or rostering.\n* Train Parts: The basic parts of a train with the same characteristics such as formation and operating period. The train part includes the actual information regarding the path of the train as a sequence of operation or control points together with the corresponding schedule information.\n* Trains: One or more train parts make up a train and represent either the operational or the commercial view of the train run.\n* Connections: The relevant connections/associations between trains at a particular operation or control point.\n* Rostering: Train parts can be linked to form the circulations necessary for rostering (rolling stock schedules).\nA list of use cases for the {{rml}} timetable schema can be found on page [[:Category:Use case (TT)]].\n\n=== Common (CO) ===\n{{main|Common}}\nThe [[Common]] class shall cover all topics, which affect all other railML-schemas alike.\n\nThe actual planned tasks and enhancements can be found in {{ticket|2=2|3=the {{#vardefine:space|{{#if:2| }}}}railML<sup><small>\u00ae</small></sup>{{#var:space}}2 ticket system}} and {{ticket|2=3|3=the {{rml|3}} ticket system}} respectively.\n\nPlease note that 2023-04-24 Common was split into Common and Generic due to technical reasons <ref> {{commit|a881cdcfa4dcc1a6de061b304d17147dfd688b7f}} </ref>\n\n== Codelists ==\n{{main|dev:Codelists|Codelists}}\nCertain attributes require a choice from a vast, highly standardized but shifting set of values. For instance, there are many regional {{external|https://en.wikipedia.org/wiki/Loading_gauge|clearance gauge standards}}. As to facilitate the usage and update of the sets, this Information is outsourced into [[dev:Codelists|codelists]] outside the {{rml}} schema.\n\nThe codelists are identically available for {{rml|2}} and {{rml|3}}.\n\n==Versions==\nThe current {{rml|3}} version is {{current}}. For {{rml|2}} see [[wiki2:|here]]. For more details see {{site|https://www.railml.org/en/developer/version-timeline.html|our version timeline}}. The development of {{rml|3}} can be tracked on {{site|https://development.railml.org/railml/version3}}. {{rml}} is licensed dually under a restricted form of the Creative Commons License ''CC-BY-NC-ND'' and a commercial license. An overview of the regarding licenses can be found under {{site|https://www.railml.org/en/user/licence.html}}.<!-- To learn about the version history and the changes between the respective versions see [[Dev:changes]].-->\n\n== Users and Developers Guides ==\n*[[Dev:How to join, edit and create the railML wiki|How to join, edit and create the railML wiki]]\n*[[Dev:Wiki Documentation Guidelines|Wiki Documentation Guidelines]]\n*[[Dev:Special Wiki Markup|Special Wiki Markup]]\n* [[RailML3_Wiki:Statistics|Statistics]]\n\n==Contact==\nFeel free to direct any comments, questions or remarks to the coordinators of {{rml}}.\n\nFor our contact information see ''[[wiki2:wiki.railML.org:Contact|Contact]]''\n\n== References ==\n<references />\n\n\n<hr>\nEnjoy the Wiki!\n\n\n[[railml2:Main Page]]",
"text_bytes": 10183,
"content_model": "wikitext",
"language": "en",
"heading": [
"Welcome to the railML\u00ae 3 wiki / Willkommen im railML\u00ae 3-Wiki",
"Current railML\u00ae subschemas",
"Interlocking (IL)",
"Infrastructure (IS)",
"Rollingstock (RS)",
"Timetable and Rostering (TT)",
"Common (CO)",
"Codelists",
"Versions",
"Users and Developers Guides",
"Contact"
],
"opening_text": null,
"auxiliary_text": [
"",
"XML Railway exchange format https://railML.org Latest release: 3.2 (April 26th, 2022)",
"\u00a0 Main Menu \u00a0 Subschemas Infrastructure Interlocking Rollingstock Timetable (Common) (Codelists) XML tree UML diagrams Use cases Versions\u00a0&\u00a0Changes",
"railML\u00ae (railway Markup Language) is an open, XML based data exchange format for data interoperability of railway applications. For further information please visit the official project website or Wikipedia. This wiki is dedicated to all Versions of railML\u00ae 3. A separate wiki for railML\u00ae 2 is available here. This wiki should support you in the development of railML\u00ae 3 interfaces and inform you about the basic elements and modelling concepts of the railML\u00ae 3 schema. You are invited to contribute to this wiki and to the development of the railML\u00ae schema. Please, see our guideline \"How to join the railML wiki\" to get to know the standards of railML's wiki and the procedure for getting a writer's account. You can find further guidelines on railML\u00ae in section #Users_and_Developers_Guides. This wiki is currently being kept only in English. railML\u00ae (railway Markup Language) ist ein offenes, XML-basiertes Datenaustauschformat zur gegenseitigen Ben\u00fctzbarkeit der Daten von Anwendungen im Eisenbahnbereich. F\u00fcr weitere Informationen besuchen Sie bitte die offizielle Projektwebsite oder Wikipedia. Dieses Wiki ist s\u00e4mtlichen Versionen von railML\u00ae 3 gewidmet. Ein separates wiki f\u00fcr railML\u00ae 2 finden Sie hier. Ziel dieses Wikis ist, Sie bei der Entwicklung von railML\u00ae 3-Schnittstellen zu unterst\u00fctzen und Sie \u00fcber die grundlegenden Elemente und Modellierungskonzepte des railML\u00ae 3-Schemas zu informieren. Sie sind herzlich eingeladen, sich an der Entwicklung dieses Wikis sowie des railML\u00ae-Schemas zu beteiligen. Lesen Sie dazu bitte unseren Leitfaden \u201eHow to join the railML\u00ae wiki\u201c, um sich mit den Standards des railML\u00ae-Wikis vertraut zu machen und die Vorgangsweise zur Erteilung eines Autorenaccounts kennenzulernen. Weitere Leitf\u00e4den, die railML\u00ae betreffen, finden Sie im Abschnitt #Users_and_Developers_Guides. Dieses Wiki wird derzeit ausschlie\u00dflich auf Englisch gef\u00fchrt."
],
"defaultsort": null,
"display_title": null,
"redirect": [
{
"namespace": 0,
"title": "Hauptseite"
}
],
"incoming_links": 5
}
}
]
}
}
}
}