Search results

The element documentation has been changed. The parents have changed. The attributes have been changed.

The element documentation has been changed. The attributes have been changed.

See anchor in RailTopoModel®'s wiki. The element documentation has been changed. The attributes have been changed. In The RailTopoModel® wiki <RTM:lin

*), typeDesignator (0..*), width (0..*) Attributes: basedOnTemplate: reference to a template platform (optional; xs:string; patterns: (urn:uuid:)?[0-9a

a "basic" train detection element and make use of the attribute @basedOnTemplate referencing to this train detection element from other (specific) train

spotLocation (0..*), typeDesignator (0..*) Attributes: basedOnTemplate: reference to a template train protection element/system (optional; xs:string; patterns:

from train side (action of train driver required), basedOnTemplate: reference to a template level crossing (optional; xs:string; patterns: (urn:uuid:)

following template: {{Deu | <deutscher-text>}} example: {{Deu | Deutsche Erläuterung}} results in Deutsche Erläuterung Please, use Template:rml for displaying

(elements)? Template If you edit an older use case, please stick to the following structure. To get an impression how to employ the templates of this list

working with railML®, we use extensive markup templates. Thus the ‘Edit’ button limits you to open the template editor and modify parameters in the source

should be used for a header or introduction. The headline is made with Template: UC title (type {{UC title}}) What is the application behind the use case

TT:textToSpeechTemplate of railML® version 3.2 UML-visualization of TT Documentation Allows specification of a text to speech template to be used by system

with the "Depr"-Template. Adjust the XML-Tree — look for help here new or changed sub-element Change the "children" with an "Intro"-Template of the next proposed

signalConstruction (0..1), spotLocation (0..*), typeDesignator (0..*) Attributes: basedOnTemplate: reference to a generic signal (optional; xs:string; patterns: (urn:uuid:)

made with Template: UC description (type {{UC description}}) In this section the data flows should be drafted. The headline is made with Template: UC flows

procedure can be found here. In special cases, you can employ a template that is based on Template:ElementDocu as to inherit certain data. Read here, how to

opOperations (0..1), spotLocation (0..*), typeDesignator (0..*) Attributes: basedOnTemplate: references a generic operational point (optional; xs:string; patterns:

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

railML® 2.4 Changes between railML® 2.4 and railML® 2.5 Please, employ template:change to add entries. The changes between the railML® 3 minor versions

The purpose of this example is twofold. It shall teach newcomers principles of modelling topologies with railML® 3. As for the proficient users, this tutorial