TT:rostering

From railML 2 Wiki
Revision as of 13:42, 23 November 2011 by RailML Superseded Users (talk | contribs) (Created with comments from the schema)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


rostering
 


Scheme description / Schemenbeschreibung

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

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

The element <rostering> contains all data, which are related to a rostering. The item is referenced via its attribute id.

In dem Element <rostering> werden alle Informationen für einen Umlaufplan beschrieben. Die einzelnen Datensätze können über das Attribut id referenziert werden.

Attributes of rostering / Attribute von rostering

  • 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.
  • vehicleRef: This is the reference to id of a default vehicle. It is normally identical for all blockParts, but can be superset by a certain blockPart. It has to follow the constraints of xs:IDREF.
  • formationRef: This is the reference to id of a default formation. It is normally identical for all blockParts, but can be superset by certain blockPart. It has to follow the constraints of xs:IDREF.
  • depot: This is the depot or location the rostering belongs to.
  • defaultPreProcessingTime: This is the default duration from the beginning of blocking of the ressource until start of blockPart. It has to allow the constraints of xs:duration.
  • defaultPostProcessingTime: This is the default duration from the end of blockPart until the end of blocking of the ressource. It has to follow the constraints of xs:duration.
  • scope: This is for the "constraint level" of the rostering.
  • conceptional
  • operational
  • timetable

Syntactic Constraints / Syntaktische Beschränkungen

id is mandatory.

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.