Search results
Jump to navigation
Jump to search
- UC:Use cases (section What is a use case?)IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source page If you want to reactivate your inactive use case10 bytes (287 words) - 16:31, 3 February 2020
- status=approved. Implement a seperate semantic constraint for every rule. Use the template with all mandatory arguments according to Template:SemanticConstraint10 bytes (579 words) - 15:58, 18 May 2020
- recommended to use the XML comments for non-content related documentation, e.g. contact information: <!-- ... --> (line 4) It is recommended to use the XML Schema10 bytes (2,659 words) - 17:25, 30 May 2022
- Main Page (section Common (CO))Creating instructions for new railML® elements Guideline on Use cases — what is a use case, where to find them and how to contribute to them. Certification9 KB (916 words) - 12:29, 22 February 2024
- Dev:identities (redirect from CO:identities)name="TGV-ICE3">... Please use some more generic coding style in order to not invite the importing software to parse the id values! Please use a generic coding style7 KB (807 words) - 19:07, 22 January 2024
- language used for name and description. Use <additionalName> to provide a name and/or description in other languages. begin: This is usually used only if12 KB (1,612 words) - 12:52, 14 May 2024
- New users Guide Dev:Use case example Shows and explains the structure of a good use case All Experienced users Guide Dev:Use cases How to contribute to8 KB (25 words) - 18:35, 5 February 2024
- namespace. How to use it? blockRef xs:IDREF, mandatory startDate xs:date, optional; shall be lower or equal endDate if both are used. endDate xs:date,5 KB (632 words) - 12:51, 14 May 2024
- Dev:Codelists (redirect from CO:codelists)all information that is collected about the ÖBB in the code list, in this case name, country code and company code: <infrastructureManager code="ÖBB"> <name>ÖBB10 bytes (797 words) - 12:25, 24 January 2020
- Dev:Changes (redirect from CO:Changes)versions started in 2001. Version 1.0, the first version allotted for productive use, was published in 2005. In 2019, the development was forked into the established10 bytes (403 words) - 16:31, 18 May 2020
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category Use case (TT)) (section Use case / Anwendungsfall)Rostering Related subschemas: IS RS CO Reported by: IVU For general information on use cases see UC:Use cases10 bytes (209 words) - 16:12, 3 February 2020
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category Use case (TT)) (section Use case / Anwendungsfall)data Typically, the import is done manually using a file based interface. Common Infrastructure: the import uses elements from mesoscopic and macroscopic10 bytes (355 words) - 16:12, 3 February 2020
- Dev:versioning (redirect from CO:versioning)ema/railML.xsd"> ... </railml> Use the last released version number plus the current SVN number: version="2.1r416" Use the last released namespace as default3 KB (198 words) - 10:42, 13 March 2024
- other standards (external link). This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other1 KB (474 words) - 19:49, 5 January 2024
- Dev:TrainProtectionSystems (redirect from CO:Codelist:TrainProtectionSystems)railML® website). The code lists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity10 bytes (422 words) - 21:38, 23 January 2020
- Dev:Registers (redirect from CO:Codelist:Registers)practical use and maintenance by the registry is guaranteed. The further procedure is explained on the dev:Codelists#Missing_entries page. Use of a project-specific10 bytes (721 words) - 21:27, 23 January 2020
- Dev:TrainClearanceGauges (redirect from CO:Codelist:TrainClearanceGauges)railML® website). The code lists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity10 bytes (294 words) - 21:36, 23 January 2020
- Dev:versions (redirect from CO:versions)as <infrastructure>, <rollingstock>, <timetable>. This attribute is to be used for the version number of the railML® schema the XML file is based on. Major10 bytes (1,043 words) - 11:29, 15 February 2023
- "Recommended best practice is to use a controlled vocabulary such as RFC 4646 (external link)." railML® semantics This may be used for identifying the default249 bytes (731 words) - 18:01, 26 February 2017
- Dev:fileConventions (redirect from CO:fileConventions)tools in productive use shall use *.railml for files / exports. *.xml is always allowed since railML® files are xml files. It shall be used for non-certified10 bytes (1,742 words) - 15:07, 13 October 2022