MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "TT:UC:ATimetableForACompetition",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "76": {
                "pageid": 76,
                "ns": 0,
                "title": "Rollingstock",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "{{navi}}\n==Rollingstock (RS)==\n[[RS:rollingstock|RS root element]] \u2014 [[RS:UseCases|RS use cases]] \u2014 [[#Documentation|Concepts & examples]]\n=== General Information ===\n\nThe rollingstock subschema is part of the complete {{site|https://www.railml.org|railML}} schema providing a data structure in XML language for the exchange of railway specific data.\n\nThe 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 {{CO:Tag|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 {{RS:Tag|rollingstock}}, which is the root for data about any rolling stock.\n\nIt is intended to use this data schema for vehicle management as well as for detailed run-time calculations. Depending on the purpose only the {{RS:Tag|vehicles}} branch of the data tree may be populated or the {{RS:Tag|formations}} branch appears or both of them. The {{RS:Tag|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 {{RS:Tag|formations}} branch is used to reflect the characteristics an entire train or a composition of vehicles within a train.\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:# vehicle as black box (with respect to dynamic characteristics) with only mean values\n:# vehicle as black box (with respect to dynamic characteristics) with curves for particular values being variable within the operating range\n:# vehicle as white box 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\nPlease visit the {{site|https://www.railml.org|railML-Website}} for more detailed information about the Rollingstock subschema or send an [mailto:coord@rollingstock.railml.org email] to the coordinator of the subschema.\n=== Documentation ===\nFor more information please refer to the following pages:\n* {{RS:Tag|rollingstock}} \u2014 documentation of the main element\n:* [[:Category:Rollingstock_Elements|Rollingstock Elements]] \u2014 overview off all XML elements found in the rollingstock subschema\n* [{{uml|RS}} UML visualization of the current {{rml|3}} RS subschema]\n<!--* Rollingstock Concepts \u2014 explanations of some basic modelling concepts to this subschema (planned)-->\n* A list of [[dev:Use Cases|use cases]] for the {{rml}} rollingstock scheme can be found here [[:Category:Use_case_(RS)]].\n*{{site|https://www.railml.org/en/user/exampledata.html|Examples}} \u2014 collection of examples provided by the {{rml}} partners\nAll elements in the Wiki are documented with the elment name and the prefix of their subschema (''RS:'' for timetable) \u2014 e.g. the wiki documentation for {{RS:Tag|vehicle}} is found here: [[RS:vehicle|https://{{thiswiki}}.railml.org/wiki/RS:vehicle]]\n\n{{interwiki}}"
                    }
                ]
            },
            "2433": {
                "pageid": 2433,
                "ns": 0,
                "title": "TT:PreliminaryDocumentation",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "This is the page for the preliminary documentation of {{rml|3.2}} [[Timetable]] scheme concepts.\n\n{{Under construction|date=2020-05-27|topic=Add description of priciples and elements|user=[[User:Coordination|Coordination]] ([[User talk:Coordination|talk]]) 15:15, 27 May 2020 (CEST)}}\n\n{{note|Please note, that this page is made for saving ideas, concepts and descriptions for the upcoming {{rml|3.2}} [[Timetable]] scheme. This page shall be replaced by the official documentation inside this wiki and must not be used for development or certification pourposes.|error}}\n\n= <commercialScheduling> =\n== Semantic constraints ==\n# all <operationalTrainSectionPart> elements referenced by one <commercialScheduling> element must belong to the same <operationalTrainSection> element\n# a <commercialScheduling> links one <commercialTrainSection> and one <operationalTrainSection> (indirectly via reference to one or more <operationalTrainSectionPart> elements). Both must reference the same <itinerary> with an identical offset \n# if more than one <commercialScheduling> elements reference the same <commercialTrainSection>, they must not overlap each other locally\n# if more than one <commercialScheduling> elements reference the same <operationalTrainSection> (indirectly via reference to <operationalTrainSectionPart>), they must not overlap each other locally\n\n= Task 2 =\n== Task 2.1 ==\n== Task 2.2 ==\n\n= Task 3 =\n== Task 3.1 ==\n== Task 3.2 ==\n== Task 3.3 =="
                    }
                ]
            }
        }
    }
}