Template:StopDescription: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(Documentation) |
|||
| Line 16: | Line 16: | ||
{{StopDescription}} | {{StopDescription}} | ||
[[Category: | [[Category:Template for semantic constraints]] | ||
</noinclude> | </noinclude> | ||
Revision as of 13:58, 19 August 2019
Usage
Template for semantic constraints of <stopDescription>
Arguments
None
Example
{{StopDescription}}
produces
The following table summarises the semantical constraints between the attributes <ocpTT>.ocpType, <stopDescription>.guaranteedPass, .commercial, .onOff, .stopOnRequest and .operationalStopOrdered:
File:Rml stopDescription en constraints.png
- Green cells are default values.
- ocpType='begin','end' are deprecated from railML 2.2.
- If no <stopDescription> is given, it is either a non-guaranteed pass (1.2) or a stop with undefined properties, depending on the attribute ocpType.
- The term "commercial" of the attribute in railML traditionally refers to the contractual relationship between RU and end-customer, not to the contractual relationship between IM and RU.
- The term "ordered" in the attribute operationalStopOrdered refers to the contractual relationship between IM and RU.