IS:propOperational: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
(Die Seite wurde neu angelegt: {{elementDocu| elementName = propOperational |parent = {{DocIS|ocp}} |childs = {{DocIS|uptime}} |ownAttributes = * {{attr|operationalType}}: a keyword that defines th...) |
No edit summary |
||
| Line 14: | Line 14: | ||
** '''blockPost''': an ocp without block signale where the train sequence is monitored (German: "Zuglaufmeldestelle") | ** '''blockPost''': an ocp without block signale where the train sequence is monitored (German: "Zuglaufmeldestelle") | ||
** '''blockSignal''': an ocp consisting of a block signal only (German: "Zugfolgestelle" / "Blockstelle") | ** '''blockSignal''': an ocp consisting of a block signal only (German: "Zugfolgestelle" / "Blockstelle") | ||
* {{attr|trafficType}}: a keyword that defines the kind of traffic for this OCP ({{xsdType|string}}, optional); possible values: | * {{attr|trafficType}}: a keyword that defines the kind of traffic for this OCP ({{xsdType|string}}, optional); possible values: | ||
| Line 29: | Line 28: | ||
|notes = | |notes = | ||
Not all combinations of {{attr|operationalType}} and {{attr|trafficType}} make sense. E. g. a station with traffic type "shunting" is not plausible. Therefore, the following | |||
}} | }} | ||
Revision as of 21:44, 28 September 2009
propOperational
Scheme description / Schemenbeschreibung
Position of propOperational in the XML-Tree / Position von propOperational im XML-Baum
Multiplicity / Anzahl
Semantics / Bedeutung
<propOperational> is a contains attributes which further refine the operational properties of an <ocp>.
Attributes of propOperational / Attribute von propOperational
- operationalType: a keyword that defines the operational function of this OCP (xs:string, optional); possible values:
- station: a regular passenger station
- stoppingPoint: an ocp without tracks where trains start, stop or end e. g. for passenger exchange (German: Haltepunkt)
- depot: a train depot
- crossover: a connection between two tracks of a double-track line (German: "Überleitstelle")
- junction: joining/splitting of two lines (German: "Abzweigstelle")
- blockPost: an ocp without block signale where the train sequence is monitored (German: "Zuglaufmeldestelle")
- blockSignal: an ocp consisting of a block signal only (German: "Zugfolgestelle" / "Blockstelle")
- trafficType: a keyword that defines the kind of traffic for this OCP (xs:string, optional); possible values:
- 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
- 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. (xs:boolean, optional)
- 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). (xs:boolean, optional)
Syntactic Constraints / Syntaktische Beschränkungen
Not yet described. / Noch nicht beschrieben.
Best practice & Examples / Empfohlene Anwendung & Beispiele
Not yet described. / Noch nicht beschrieben.
Notes / Anmerkungen
Not all combinations of operationalType and trafficType make sense. E. g. a station with traffic type "shunting" is not plausible. Therefore, the following
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.