Search results

dependency is essential for the use case or considered optional. Please describe what data is exchanged for the use case. What is part and what is not part

edit an older use case, please stick to the following structure. To get an impression how to employ the templates of this list see Dev:Use case example/old

good use case. For an actual example see UC:IS:Schematic Track Plan. To get more information on use cases and how to describe them, see Dev:Use cases. Please

and Developer Pages   This page provides an overview over pages from the Dev-namespace that offer User Guides, information for developers and connected

Sharing Dev:Types of ocps Dev:UML Dev:Units Dev:Usage of the track between the stations Dev:Use case example/old Dev:Use cases Dev:UsingAny Dev:Wiki Documentation

with us. To learn where to find, how to use and how to contribute use cases see Dev:Use cases. While use cases follow a top-down approach, starting out

The railML® wiki offers a number of Use Cases. A Guideline to implementing Use Cases can be found under Dev:Use cases. In contrast to railML® 2, railML®

personResponsible must occur once. (line 17) In case the element contract is used the elements number and requirement have to be used, too. The element requirement may

references across files and data sources. In case of valid railML® files, no problems will occur. In case of consuming "good or bad styled" id values the

semantic constraint on the respective list below (Dev:Semantic_Constraints/table2 for railML® 2 and Dev:Semantic_Constraints/table3 for railML® 3). assign

(character sub-set) follows implicitly from the characters used in the name. So, the only case when to use the script sub-tag is to distinguish between two <additionalName>

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>ÖBB

infrastructure elements are aggregated to an <ocp> depends on the context (use case) and the accuracy requirement of the timetable. Timetables that aim more

trainPart is in the best case redundant, if it is used as a shortcut to the commercial train number. The recommended practice is to use trainNumber only on

Infrastructure Rollingstock Timetable (Common) (Codelists) XML tree UML diagrams Use cases Versions & Changes

Article: Dev:Versions The development of the early alpha versions started in 2001. Version 1.0, the first version allotted for productive use, was published

single-track railway lines with regular traffic in both directions. In that case, please use value "none" in order to mark that there is no preferred driving direction

values of the connected <trackBegin> and <trackEnd> must be identical just in case both are provided and no mileageChange at this point is defined and both

most useful when shipping the railML® document as a zip archive. In this case the image resource can be provided along with the actual document. If the

values can be given per vehicle. In case of vehicles with interchangeable track gauge the value for the gauge mainly used shall be given. Additional information