Search results

elements necessary for the use case. This description may also reference other existing use cases. Are there any partial use cases distinguished, which build

or not at all at the certain position. (line 12) The element personResponsible must occur once. (line 17) In case the element contract is used the elements

This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity. A related use case will

tracks Remarks and open issues on mileage changes (planned) IS:UseCases — a collection us use cases for the IS-subschema Examples (link to the railML® website)

(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>

off all XML elements found in the rollingstock subschema UML visualization of the current railML® 2 RS subschema RS:UseCases — a collection of use cases

railML® How to define track usage of a train in stations UC:Use cases/table — a collection us use cases for the TT-subschema Examples (link to the railML® website; login

what kind of register is used to identify an <ocp> if more than one would apply. Nevertheless, also if @code is used the same 3 cases need to be distinguished

reflect the as-built situation. Please refer to the linked use cases that cover the Eulynx use case. For detailed information please refer to the website https://eulynx

other standards (external link). This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other

status=approved. Implement a seperate semantic constraint for every rule. Use the template with all mandatory arguments according to Template:SemanticConstraint. Record

(typically the same line and same owner). If absPos is used in <trackEnd> then it should be used in <trackBegin> for unambiguity reasons, too. absPosOffset:

cable plan Subschema: Interlocking For general information on use cases see UC:Use cases

the attributes @absPos and @absDir of the element <trackBegin> are used. Do not use a <mileageChange> at the beginning of a track, if you do not have any

Visualisation (RAIV) Subschema: Infrastructure For general information on use cases see UC:Use cases

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

von Schienenanlagen railML data will be used for engineering signalling and interlocking systems. Engineers are used to working with paper plans that schematically

interlocking, 10 – 15 RINF parameter types for utilization restrictions, all along with a determined time validity.)

suppliers; Austausch von Planungsparametern für Stellwerke mit Anbietern All the planning parameters, which are necessary to build an interlocking (hard-

subschemas: IS RS  Reported by: PSI For general information on use cases see UC:Use cases