IS:infrastructure

From railML 2 Wiki
Jump to navigation Jump to search


infrastructure
 


Schema description / Schemenbeschreibung

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

Multiplicity / Anzahl

[0..1]

Semantics / Bedeutung

An <infrastructure> defines the header container for all infrastructure elements and attributes. This may contain also infrastructure that is not yet, temporarily, or no longer in operation.
 
Please, be aware of the semantic constraint(s)!

Attributes of infrastructure / Attribute von infrastructure

  • 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.
  • 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.
  • version: This is the version number of the railML® release the current XML file conforms to. It is not any internal numbering from a version control system for the data version. Use it only, if the subschema element is outsourced, else use the 'version' attribute in the root element (<railml>)


  • timetableRef: This refers to the id attribute of the associated <timetable> element.

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


  • version: optional, two or three part version numbers, e.g. 1.0 up to 99.99, or 1.0.1 up to 99.99.99

Semantic Constraints / Semantische Beschränkungen

Private-cloud-icon.png Semantic Constraint "IS:017":
 

either <infrastructure> or <railml> must have @version attribute

Compare #xxx
 
Proposed on March 25th 2024
Approved on March 25th 2024
FIXME: add Link to discussion!
Please, recognize our guidelines on semantic constraints

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

An infrastructure is divided into tracks, trackGroups and operationControlPoints.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.