Search results
Jump to navigation
Jump to search
- Talk:Dev:InfrastructureManagers (category Common Concept)the code attribute of the following elements: Common subschema <infrastructureManager> railML® 3 Common subschema <infrastructureManager> <organizationalUnit>23 KB (302 words) - 10:42, 12 July 2023
- elements in a bottom-up approach, we also try to help users to capture the concepts of railML® via examples and use cases in a top down approach. A use case7 KB (287 words) - 16:17, 13 May 2024
- Modells und Austauschformates gegeben werden. An extended example, which shows common elements of railway operation that are used in data management and data5 KB (674 words) - 15:49, 15 April 2024
- Main Page (section Common (CO))schema can be found on page Category:Use case (TT). →Main Article: Common The Common class shall cover all topics, which affect all other railML-schemas10 KB (1,041 words) - 10:56, 2 May 2024
- <timetablePeriod> defined for one year as a place-holder for all the years. This is common practice if seasonised trains operate, e. g. school trains or summer-only16 KB (1,903 words) - 13:27, 13 March 2023
- 2023 (CEST) Common (wiki2; wiki3) ✔ Infrastructure (wiki2; wiki3) ✔ Rollingstock (wiki2; wiki3) ✔ Timetable (wiki2; wiki3) ✔ Dev:Common Concepts (wiki2; wiki3)5 KB (363 words) - 14:51, 24 April 2023