RS:formation: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
m (new attributes)
m (template for inherited attributes)
Line 14: Line 14:


|inheritedAttributes =
|inheritedAttributes =
* {{attr|id}}: Unique identifier which is used to refer to this particular item. This ID is always required for the item. It is inherited as a common feature from the type [[tElementWithIDAndName]].
{{inheritIdName}}
 
* {{attr|name}}: A short name for the item can be given here, if wanted. It is inherited as a common feature from the type [[tElementWithIDAndName]].
 
* {{attr|description}}: In addition to a short name a more detailed description can be given here. This shall allow a short overview or hints to the contents of this dat set. It is inherited as a common feature from the type [[tElementWithIDAndName]].


|ownAttributes =
|ownAttributes =

Revision as of 13:26, 12 February 2011


formation
 


Scheme description / Schemenbeschreibung

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

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

The element <formation> contains all data related to a composition of single vehicles forming a complete train or a part of a train. It is not excluded to describe a train consisting of only one single vehicle.

Im Element <formation> werden alle Zug bezogene Daten aufgenommen. Dabei kann es sich wirklich um einen kompletten Zug oder nur um einen Zugteil aus mehreren Einzelfahrzeugen handeln. Es ist aber auch möglich einen nur aus einem Fahrzeug bestehenden Zug zu beschreiben.

Attributes of formation / Attribute von formation

  • 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.
  • formationCount: This is the number of formations of that type forming the train or train part. This can be used for example when a train is made up of several multiple units of the same type. In all other cases the default value is '1'.
  • length: This is the overall length in metres of that formation. The user has to ensure that it is the resulting sum of the length of each single vehicle the formation consists of.
The value can be used here just for easy access.
  • speed: This is the maximum speed in kilometres per hour permitted for that formation. The user has to ensure, that this value is not greater than any permitted speed of the single vehicles the formation consists of.
The value can be used here just for easy access.
  • weight: This is the total weight in metric tons of that formation. The user has to ensure that it is the resulting sum of the weigths of each single vehicle the formation consists of.
The value can be used here just for easy access.
  • bruttoWeight (> 2.0): This is the total brutto weight (vehicles plus payload) in metric tons of that formation. The user has to ensure that it is the resulting sum of the weigths of each single vehicle the formation consists of.
  • nettoWeight (> 2.0): This is the total net weight (payload only) in metric tons of that formation. The user has to ensure that it is the resulting sum of the weigths of each single vehicle the formation consists of.
  • tareWeight (> 2.0): This is the total tare weight (empty vehicles) in metric tons of that formation. The user has to ensure that it is the resulting sum of the weigths of each single vehicle the formation consists of.

Syntactic Constraints / Syntaktische Beschränkungen

The values of length, speed and weight can be given here, if no deeper level of details is necessary. However, the user and application has to ensure the consistancy with any redundant information given for single vehicles.

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.