Search results
Jump to navigation
Jump to search
- 3.2 UML-visualization of RAILML Documentation This is the root element of any railML file. Subschema railml Parents* Children common (0..1), infrastructure513 bytes (4 words) - 18:40, 19 December 2019
- CO:contractor (category Missing Element Documentation/CO)element CO:contractor of railML® version 3.2 UML-visualization of CO Documentation DEPRECATED with railML 3.2; use organizationalUnit instead; Any unit or513 bytes (15 words) - 18:40, 19 December 2019
- CO:isContractor (category Pages using Tabber parser tag)This 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 further515 bytes (38 words) - 16:13, 5 March 2021
- CO:positioning (category Pages using Tabber parser tag)ystem>. It is used to locate infrastructure elements within the topology network. For the mesoscopic topology, it is recommended to use the classic railway11 KB (1,110 words) - 09:59, 29 April 2024
- CO:validityTime:period (category Missing Element Documentation/CO)This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® . Do not hesitate to contact railML.org for further759 bytes (36 words) - 13:44, 18 April 2024
- IS:speedSection (category Pages using Tabber parser tag)Speed limits are modelled in railML® using speedSection elements in combination with <speedProfile> elements. The element documentation has been changed2 KB (250 words) - 18:16, 15 January 2024
- Generic:textMessage (category Pages using Tabber parser tag)generic subschema. It is available only in railML® 3.2. There exists an element <CO:textMessage> that might have preceded it. Do not hesitate to contact railML519 bytes (58 words) - 12:42, 8 February 2024
- Generic:bitmaskValidity (category Pages using Tabber parser tag)generic subschema. It is available only in railML® 3.2. There exists an element <CO:bitmaskValidity> that might have preceded it. Do not hesitate to contact railML1 KB (161 words) - 16:02, 7 March 2024
- Main Page (section Common (CO))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 or10 KB (1,041 words) - 10:56, 2 May 2024
- Generic:ownsInfrastructureElement (category Pages using Tabber parser tag)generic subschema. It is available only in railML® 3.2. There exists an element <CO:ownsInfrastructureElement> that might have preceded it. Do not hesitate to533 bytes (58 words) - 12:40, 8 February 2024
- IS:line (category Pages using Tabber parser tag)<linePerformance>, like any other elements with measurement attributes, has a specific unit given by its datatype. (i.e. @maxSpeed uses the km/h unit) The datatype9 KB (873 words) - 11:03, 13 May 2024
- Dev:Changes/3.2 (category Pages using DynamicPageList3 parser function)CO:alternative CO:approvedBy CO:checkedBy CO:etcsSpeedProfile CO:holiday CO:holidays CO:isConcessionaire CO:isContractor CO:isCustomer CO:isInfrastructureManager3 KB (756 words) - 14:47, 27 June 2022
- Autoexport from the XML-Schema for element CO:isContractor of railML® version 3.2 UML-visualization of CO Documentation Any unit or undertaking that has a binding694 bytes (5 words) - 21:49, 25 April 2022
- element CO:contractor of railML® version 3.2 UML-visualization of CO Documentation DEPRECATED with railML 3.2; use organizationalUnit instead; Any unit or2 KB (5 words) - 12:39, 8 February 2024
- forum and the proposed constraint will be added to the element documentation using Template:Semcon, with status=proposed and added to the list below. If there4 KB (579 words) - 16:49, 13 March 2023
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category AllUseCases) (section Use case / Anwendungsfall)Common Infrastructure Rolling stock could be daily small (single train run) any see _Import complete timetable for vehicle working scheduling_ We describe2 KB (209 words) - 18:11, 27 June 2022
- standardized link for Any-elements (see CO:usingAny to learn, what this is). {{Any}} delivers any () {{Any|multiplicity=0..1}} delivers any (0..1)394 bytes (27 words) - 17:28, 28 February 2020
- Template:UseCase (category AllUseCases)argument, telling you, to which subschema the use case belongs. Use the abbreviation IS, IL, TT, RS or CO 2: obligatory, unnamed argument, telling you,3 KB (219 words) - 17:55, 15 April 2024
- <trainProtectionElement> shall only be used for national and/or legacy train protection systems. ETCS-based systems must not be modeled using <trainProtectionElement>9 KB (3 words) - 12:19, 13 May 2024