Search results

172de2c1">... Please note: a Nil UUID () shall not be used; UUID's Version 4 () is commonly used. Sometimes exporting software tools create id values,

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

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

value is used in case of any TVD section of the route is also used by the conflicting one. ConflictingHeadProtection – This value is used in case any signal

The block signal is used on open line at the start of a block route. blockInterface - This signal is in most cases a virtual signal used to transfer the actual

is the reference to the physical end of the route path. This is in most cases a signal but can also be a buffer stop or just a train detection device when

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

route lock is only applied when a train is approaching the route. In that case this time is the minimum required before the final route lock can be applied

<signalIL> which protects the exit from this TVD section. It shall be used in case @isBerthingTrack is set to true. Within the simple example there are

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®

a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please

– In most cases the preferred position of a level crossing is open, i.e. allowing road traffic to pass freely. However, there might be cases when the level

the same time in case of coupled switches. @preferredPosition – This marks the switch position that the switch shall have when not in use of a route. The

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

They deliver mainly the status information vacant, occupied or failed. In case of a failure the particular sections needs to be reset, i.e. declared clear

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

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

conflictingHeadProtection: This value is used in case any signal that shall provide flank/head protection to either route is used as route destination for the other

certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity errors. For instance in railML® 2, using <infrastructureManager>

elements. Within the entire railML schema there are no different namespaces used. Subsequently some elements (types) in interlocking subschema had to be renamed