IS:propOperational: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
No edit summary
(Updated using schema contents and new templates)
Line 1: Line 1:
{{elementDocu|
{{ElementDocu|
elementName = propOperational
elementName = propOperational
|parent = {{DocIS|ocp}}


|childs = {{DocIS|uptime}}
|parent = {{IS:Tag|ocp}}
 
|childs = {{IS:Tag|uptime}}
 
|semantics =
{{IS:Tag|propOperational}} contains attributes which further refine the operational properties of an {{IS:Tag|ocp}}.


|ownAttributes =
|ownAttributes =
* {{attr|operationalType}}: a keyword that defines the operational function of this OCP ({{xsdType|string}}, optional); possible values:
* {{Attr|operationalType}}: This is a keyword that defines the operational function of this {{IS:Doc|ocp}}. Possible values are:
** '''station''': a regular passenger station
:* {{Enum|station}} a regular passenger station
** '''stoppingPoint''': an ocp without tracks where trains start, stop or end e. g. for passenger exchange (German: Haltepunkt)
:* {{Enum|stoppingPoint}} an {{IS:Doc|ocp}} without {{IS:Doc|track}}s where {{TT:Doc|train}}s start, stop or end e. g. for passenger exchange <br/> {{Deu|"Haltepunkt"}}
** '''depot''': a train depot
:* {{Enum|depot}} a train depot
** '''crossover''': a connection between two tracks of a double-track line (German: "Überleitstelle")
:* {{Enum|crossover}} a {{IS:Doc|connection}} between two {{IS:Doc|track}}s of a double-track line <br/> {{Deu|"Überleitstelle"}}
** '''junction''': joining/splitting of two lines (German: "Abzweigstelle")
:* {{Enum|junction}} joining/splitting of two {{IS:Doc|line}}s <br/> {{Deu|"Abzweigstelle"}}
** '''blockPost''': an ocp without block signale where the train sequence is monitored (German: "Zuglaufmeldestelle")
:* {{Enum|blockPost}} an {{IS:Doc|ocp}} without block signal where the {{TT:Doc|train}} sequence is monitored <br/> {{Deu|"Zuglaufmeldestelle"}}
** '''blockSignal''': an ocp consisting of a block signal only (German: "Zugfolgestelle" / "Blockstelle")
:* {{Enum|blockSignal}} an {{IS:Doc|ocp}} consisting of a block {{IS:Doc|signal}} only <br/> {{Deu|"Zugfolgestelle"/"Blockstelle"}}
:* {{OtherEnum
|notes_en =
|notes_de =
}}


* {{attr|trafficType}}: a keyword that defines the kind of traffic for this OCP ({{xsdType|string}}, optional); possible values:
* {{Attr|trafficType}}: This is a keyword that defines the kind of traffic for this {{IS:Doc|ocp}}. Possible values are:
** '''passenger''': the prevailing traffic occuring at this OCP is passenger traffic
:* {{Enum|passenger}} the prevailing traffic occuring at this {{IS:Doc|ocp}} is passenger traffic
** '''freight''': the prevailing traffic occuring at this OCP is freight traffic
:* {{Enum|freight}} the prevailing traffic occuring at this {{IS:Doc|ocp}} is freight traffic
** '''shunting''': the prevailing traffic occuring at this OCP is shunting traffic, e. g. in a depot or a workshop
:* {{Enum|shunting}} the prevailing traffic occuring at this {{IS:Doc|ocp}} is shunting traffic, e. g. in a depot or a workshop
:* {{OtherEnum
|notes_en =
|notes_de =
}}


* {{attr|orderChangeable}}: if true, the OCP is capable of changing the train sequence on the open track. That means that the OCP has at least one point. ({{xsdType|boolean}}, optional)
* {{Attr|orderChangeable}}: if true, the {{IS:Doc|ocp}} is capable of changing the {{TT:Doc|train}} sequence on the open {{IS:Doc|track}}. That means that the {{IS:Doc|ocp}} has at least one point.


* {{attr|ensuresTrainSequence}}: if true, the OCP ensures and protects the train sequence on the open track. In other words: while the OCP is occupied by a train, a subsequent train may safely approach the OCP. The train sequence is protected. This is mostly implemented by a signal (e. g. a home signal or a block signal). ({{xsdType|boolean}}, optional)
* {{Attr|ensuresTrainSequence}}: if true, the {{IS:Doc|ocp}} ensures and protects the {{TT:Doc|train}} sequence on the open {{IS:Doc|track}}. In other words: while the {{IS:Doc|ocp}} is occupied by a {{TT:Doc|train}}, a subsequent {{TT:Doc|train}} may safely approach the {{IS:Doc|ocp}}. The {{TT:Doc|train}} sequence is protected. This is mostly implemented by a {{IS:Doc|signal}} (e. g. a home signal or a block signal).


|semantics =
|constraints =
{{IS:Tag|propOperational}} contains attributes which further refine the operational properties of an {{IS:Tag|ocp}}.
* {{Attr|operationalType}} optional
 
* {{Attr|trafficType}} optional
 
* {{Attr|orderChangeable}} {{XsdType|boolean}}, default: {{Enum|false}}, optional
 
* {{Attr|ensuresTrainSequence}} {{XsdType|boolean}}, default: {{Enum|true}}, optional


|constraints =
Not all combinations of {{Attr|operationalType}} and {{Attr|trafficType}} make sense. E. g. a stopping point with traffic type {{Enum|shunting}} is not plausible. Therefore, the following constraints apply:
Not all combinations of {{attr|operationalType}} and {{attr|trafficType}} make sense. E. g. a stopping point with traffic type "shunting" is not plausible. Therefore, the following constraints apply:


* if value of {{attr|operationalType}} in ("crossover", "junction", "blockPost", "blockSignal") ==> {{attr|trafficType}} not set
* if value of {{Attr|operationalType}} in ({{Enum|crossover}}, {{Enum|junction}}, {{Enum|blockPost}}, {{Enum|blockSignal}}) ==> {{Attr|trafficType}} not set


* if value of {{attr|trafficType}} == "shunting" ==> {{attr|operationalType}} not equal to "stoppingPoint"
* if value of {{Attr|trafficType}} == {{Enum|shunting}} ==> {{Attr|operationalType}} not equal to {{Enum|stoppingPoint}}


|backHome = IS:elements
}}
}}

Revision as of 13:53, 8 December 2011


propOperational
 


Scheme description / Schemenbeschreibung

Position of propOperational in the XML-Tree / Position von propOperational im XML-Baum

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

<propOperational> contains attributes which further refine the operational properties of an <ocp>.

Attributes of propOperational / Attribute von propOperational

  • operationalType: This is a keyword that defines the operational function of this ocp. Possible values are:
  • station a regular passenger station
  • stoppingPoint an ocp without tracks where trains start, stop or end e. g. for passenger exchange
    "Haltepunkt"
  • depot a train depot
  • crossover a connection between two tracks of a double-track line
    "Überleitstelle"
  • junction joining/splitting of two lines
    "Abzweigstelle"
  • blockPost an ocp without block signal where the train sequence is monitored
    "Zuglaufmeldestelle"
  • blockSignal an ocp consisting of a block signal only
    "Zugfolgestelle"/"Blockstelle"
  • other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.
  • trafficType: This is a keyword that defines the kind of traffic for this ocp. Possible values are:
  • passenger the prevailing traffic occuring at this ocp is passenger traffic
  • freight the prevailing traffic occuring at this ocp is freight traffic
  • shunting the prevailing traffic occuring at this ocp is shunting traffic, e. g. in a depot or a workshop
  • other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.
  • orderChangeable: if true, the ocp is capable of changing the train sequence on the open track. That means that the ocp has at least one point.
  • ensuresTrainSequence: if true, the ocp ensures and protects the train sequence on the open track. In other words: while the ocp is occupied by a train, a subsequent train may safely approach the ocp. The train sequence is protected. This is mostly implemented by a signal (e. g. a home signal or a block signal).

Syntactic Constraints / Syntaktische Beschränkungen

  • operationalType optional
  • trafficType optional
  • orderChangeable xs:boolean, default: false, optional
  • ensuresTrainSequence xs:boolean, default: true, optional

Not all combinations of operationalType and trafficType make sense. E. g. a stopping point with traffic type shunting is not plausible. Therefore, the following constraints apply:

  • if value of operationalType in (crossover, junction, blockPost, blockSignal) ==> trafficType not set
  • if value of trafficType == shunting ==> operationalType not equal to stoppingPoint

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.