Search results
Jump to navigation
Jump to search
- IL:controller (category Elements)the controller. The associations for a controller are defined with these elements: <controlledAssets> – This is the container with the lists of all assets4 KB (460 words) - 05:23, 18 April 2022
- IL:route (category Elements)included in the path. In addition there may be elements outside the (running) path of the route. These elements are overlap, flank protection, TVD sections9 KB (1,096 words) - 11:30, 30 May 2024
- IS:tunnelGateIS (category Elements)element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions658 bytes (46 words) - 08:39, 15 July 2024
- IL:hasOperatorCommand (category Elements)element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions2 KB (255 words) - 15:33, 29 October 2023
- IS:genericArea (category Elements)element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions824 bytes (73 words) - 12:46, 8 December 2023
- IL:routeRelation (category Elements)-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts3 KB (276 words) - 10:22, 30 May 2024
- IS:stoppingPlace (category Elements)-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts951 bytes (35 words) - 10:38, 19 August 2024
- CO:organizationalUnits (category Elements).*), vehicleOperator (0..*) Attributes:None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts522 bytes (4 words) - 18:40, 19 December 2019
- IS:trainProtectionElement (category Elements)-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts2 KB (16 words) - 16:46, 2 July 2024
- IS:border (category Elements)-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts706 bytes (9 words) - 18:23, 15 April 2024
- IS:mileageChange (category Elements)element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions2 KB (222 words) - 18:16, 23 May 2024
- IS:platform (category Elements)-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts977 bytes (52 words) - 17:38, 8 July 2024
- CO:infrastructureManager (category Elements)-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts524 bytes (15 words) - 18:40, 19 December 2019
- IL:combinedRoute (category Elements)data. @id - The unique identifier used to reference this element within railML. @priorityRank – The positive integer gives the priority of this path for3 KB (348 words) - 12:05, 28 May 2022
- IL:routeSequence (category Elements)element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions516 bytes (38 words) - 21:53, 25 April 2022
- IS:weightLimit (category Elements)-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts514 bytes (15 words) - 18:45, 19 December 2019
- IS:trackGauge (category Elements)-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts506 bytes (15 words) - 12:19, 15 July 2024
- IL:interlocking. A complete element list can be found under Category:Interlocking Elements The subschema is developed with the participation of some European infrastructure1 KB (153 words) - 18:26, 3 November 2023
- CO:isContractor (category Elements)element does not appear in railML® 3.1 within the CO subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions515 bytes (38 words) - 16:13, 5 March 2021
- CO:isVehicleManufacturer (category Elements)element does not appear in railML® 3.1 within the CO subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions524 bytes (38 words) - 16:13, 5 March 2021