IS:propOperational: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
(Updated using schema contents and new templates)
m (Link removed for clear hyperlink structures)
Line 14: Line 14:
:* {{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"}}
:* {{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"}}
:* {{Enum|depot}} a train depot
:* {{Enum|depot}} a train depot
:* {{Enum|crossover}} a {{IS:Doc|connection}} between two {{IS:Doc|track}}s of a double-track line <br/> {{Deu|"Überleitstelle"}}
:* {{Enum|crossover}} a connection between two {{IS:Doc|track}}s of a double-track line <br/> {{Deu|"Überleitstelle"}}
:* {{Enum|junction}} joining/splitting of two {{IS:Doc|line}}s <br/> {{Deu|"Abzweigstelle"}}
:* {{Enum|junction}} joining/splitting of two {{IS:Doc|line}}s <br/> {{Deu|"Abzweigstelle"}}
:* {{Enum|blockPost}} an {{IS:Doc|ocp}} without block signal where the {{TT:Doc|train}} sequence is monitored <br/> {{Deu|"Zuglaufmeldestelle"}}
:* {{Enum|blockPost}} an {{IS:Doc|ocp}} without block signal where the {{TT:Doc|train}} sequence is monitored <br/> {{Deu|"Zuglaufmeldestelle"}}

Revision as of 17:48, 21 January 2013


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.