IS:ocp

ocp
 

Scheme description / Schemenbeschreibung

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

• Parent: <operationControlPoints>
• Children: <additionalName> (introduced with version 2.1), <area>, <geoCoord>, <propEquipment>, <propOperational>, <propOther>, <propService>, <tsi> (introduced with version 2.1), <designator> (introduced with version 2.2)

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

An <ocp> is a container for Operation or Control Points (places). Each ocp illustrates one operation or control place in the infrastructure and has a unique ID and name.

Attributes of ocp / Attribute von ocp

• id: XML-file-wide unique, machine-interpretable identity, required for later referencing that element internally. For a detailed explanation see Dev:identities.
  XML-Datei-weit eindeutige, maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities.
• code (introduced with version 2.1): Machine-interpretable string (e.g. an abbreviation) used for identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code and human-readable identifiers.
  Maschineninterpretierbare Zeichenkette (z.B. Abkürzung), die zur Identifizierung des Objekts auch bei Austauschpartnern verwendet wird, wobei spezifische Eindeutigkeitsbeschränkungen gelten können. Bitte beachten Sie unsere Erläuterung zu den Unterschieden zwischen id, code and menschenlesbaren Kennzeichnungen.
  For more general reasons, use this generic attribute instead
• name: Established, human-readable short string, giving the object a name. Not intended for machine interpretation, please see our notice on human interpretable data fields.
  Etablierte, menschenlesbare kurze Zeichenkette, die das Objekt benennt. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
• description: Human-readable, more detailed description as addition to the name. It should give additional explanations or hints to the contents of this element. Not intended for machine interpretation, please see our notice on human interpretable data fields.
  Menschenlesbare, detailliertere Beschreibung als Ergänzung zu name. Sie soll zusätzliche Erläuterungen oder Hinweise auf den Inhalt dieses Elements geben. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
• xml:lang (introduced with version 2.1): This is a unique identifier of language. It uses basically the language standard IETF BCP 47 (external link) which may be different to ISO 639-1 (external link) or ISO 639-2 (external link). For mapping hints see relation to other standards (external link).
  This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other languages.
• number (deprecated with version 2.1): This is an arbitrary number e. g. as prefix in signal names or similar.

• abbrevation (deprecated with version 2.1): This is the abbreviation of an ocp as it used e. g. in time tables.

• timezone (introduced with version 2.1): This is the timezone as defined in the tz database, e.g. "Europe/Berlin".
  siehe auch Wikipedia Zeitzonen-Datenbank
  This timezone marks the railway time at a station regardless of the local time (outside the station), e.g. station of Kaliningrad at UTC+04 (Europe/Moscow), but the city itself at UTC+03 (Europe/Kaliningrad).

Syntactic Constraints / Syntaktische Beschränkungen

• id: xs:ID, required
  a string, starting with a letter (a..zA..Z) or an underscore (_),
  followed by a non-colonized and non-spaced string consisting of letters, digits, points (.), dashes (-) or underscores (_)
• code: xs:string, optional
• name: xs:string, optional
• description: xs:string, optional
• xml:lang: xs:language, language identification, optional

• number xs:string, optional

• abbrevation xs:string, optional

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

ocps are needed to organise railway operations. An OCP is a grouping of infrastructure elements sharing traffic or operational (interlocking) functions. So, they typically but not necessarily fit to what is commonly known as a 'station'. An OCP typically owns one ore more signal boxes and/or platforms.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.