Template:StopDescription: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Created page with "<includeonly>The following table summarises the semantical constraints between the attributes {{TT:Tag|ocpTT}}.{{Attr|ocpType}}, {{TT:Tag|stopDescription}}.{{Attr|guaranteedPa...")
 
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
<includeonly>The following table summarises the semantical constraints between the attributes {{TT:Tag|ocpTT}}.{{Attr|ocpType}}, {{TT:Tag|stopDescription}}.{{Attr|guaranteedPass}}, .{{Attr|commercial}}, .{{Attr|onOff}}, .{{Attr|stopOnRequest}} and  .{{Attr|operationalStopOrdered}}:<br>
<includeonly>The following table summarises the semantical constraints between the attributes {{TT:Tag|ocpTT}}.{{Attr|ocpType}}, {{TT:Tag|stopDescription}}.{{Attr|guaranteedPass}}, .{{Attr|commercial}}, .{{Attr|onOff}}, .{{Attr|stopOnRequest}} and  .{{Attr|operationalStopOrdered}}:<br>
[[file:rml_stopDescription_en_constraints.png<!--||semantical constraints of <stopDescription>-->]]<br>
[[File:RailML_2_stopDescription_constraints.png<!--||semantical constraints of <stopDescription>-->]]<br>
* Green cells are default values.
* Green cells are default values.
* {{Attr|ocpType}}='begin','end' are deprecated from railML 2.2.
* {{Attr|ocpType}}='begin','end' are deprecated from railML 2.2.
Line 6: Line 6:
* ''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 "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 {{Attr|operationalStopOrdered}} refers to the contractual relationship between IM and RU.''</includeonly><noinclude>
* ''The term "ordered" in the attribute {{Attr|operationalStopOrdered}} refers to the contractual relationship between IM and RU.''</includeonly><noinclude>
Template for semantic constraints of {{TT-Tag|stopDescription}}
==Usage==
Template for semantic constraints of {{TT:Tag|stopDescription}}
===Arguments===
''None''
==Example==
<pre>{{StopDescription}}</pre>
produces


[[Category:Template]]
{{StopDescription}}
 
[[Category:Template for semantic constraints]]
</noinclude>
</noinclude>

Latest revision as of 15:01, 21 April 2020

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:
RailML 2 stopDescription 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.