User:RailML Coord Documentation/Spielwiese: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 12: | Line 12: | ||
* ''The term "ordered" in the attribute {{Attr|operationalStopOrdered}} refers 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.'' | ||
{{semcon| | {{semcon|User:Ferri_Leberl/Spielwiese2|status=proposed|proposed=2018-09-03}} | ||
Revision as of 18:20, 27 March 2019
|
The following table summarises the semantical constraints between the attributes <ocpTT>.ocpType, <stopDescription>.guaranteedPass, .commercial, .onOff, .stopOnRequest and .operationalStopOrdered:
semantical constraints of <stopDescription>
- 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.
|