Difference between revisions of "TT:rostering"

Revision as of 15:47, 3 July 2019

rostering
 

Scheme description / Schemenbeschreibung / Description du schéma

Position of rostering in the XML-Tree / Position von rostering im XML-Baum / position de rostering dans l’aborescence XML

• Parent: <rosterings>

• Children: <additionalName> (introduced with version 2.1), <blockParts>, <blocks>, <circulations>, <xs:any> (introduced with version 2.1)

Multiplicity / Anzahl / Multiplicité

[1..∞]

Semantics / Bedeutung / Sémantique

The element <rostering> contains all data, which are related to a rostering.

In dem Element <rostering> werden alle Informationen für einen Umlaufplan beschrieben.

Please, be aware of the semantic constraint(s)!
 
Please, be aware of the semantic constraint(s)!

Attributes of rostering / Attribute von rostering / Attributs de 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.
  Maschineninterpretierbare Zeichenkette (z.B. Abkürzung), die zur Identifizierung des Objekts auch bei Austauschpartnern verwendet wird, wobei spezifische Eindeutigkeitsbeschränkungen gelten können.
  This is the short string which is known for identifying the rostering across the involved staff.
• 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 refers to the id attribute of the associated <vehicle> element.
  This "default vehicle" is normally identical for all blockParts, but can be superset by a certain blockPart.

• formationRef: This refers to the id attribute of the associated <formation> element.
  This "default formation" is normally identical for all blockParts, but can be superset by certain blockPart.

• 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.
  definiert die (Standard-)Vorbereitungszeit, die gilt, wenn keine abweichende Angabe bei blockPartSequence erfolgt

• defaultPostProcessingTime: This is the default duration from the end of blockPart until the end of blocking of the ressource.
  definiert die (Standard-)Nachbereitungszeit, die gilt, wenn keine abweichende Angabe bei blockPartSequence erfolgt

• scope: This is for the "constraint level" of the rostering. Possible values are:

In this article there is information missing with respect to the semantics of the enumeration items. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion page. Ferri Leberl (talk) 16:13, 25 April 2018 (CEST)

• conceptional
• operational
• timetable
• other:anything Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed.

Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques

• 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

• vehicleRef: xs:IDREF, optional

• formationRef: xs:IDREF, optional

• depot: xs:string, optional

• defaultPreProcessingTime: xs:duration, optional

• defaultPostProcessingTime: xs:duration, optional

• scope: union of (restriction of xs:string, tOtherEnumerationValue); tOtherEnumerationValue is an arbitrary string starting with 'other:' followed by at minimum two characters, white space not allowed for extending railML enumeration lists, optional

Semantic Constraints / Semantische Beschränkungen / Contraintes semantiques

Semantic Constraint:   vehicleRef and formationRef are to be used exceptional since the circulation plan is either one for a certain vehicle or one for a whole formation. Es ist nur entweder vehicleRef oder formationRef anzugeben (nicht jedoch beide gleichzeitig), da es sich entweder um einen Umlauf eines Einzelfahrzeugs oder einer Fahrzeuggruppe handelt.   Proposed on 2019-06-25 Approved on 2019-05-22 Please, recognize our guidelines on semantic constraints

Best practice & Examples / Empfohlene Anwendung & Beispiele / Bonnes pratiques & exemples

see railML-Beispiel Umlauf aus FBS (external link, May 2012, PDF, ; by Dirk Bräuer, iRFP Dresden)

Notes / Anmerkungen / Notes

Starting with version 2.4 <blocks> has been made optional in order to allow for modelling of special track occupation. See the forum discussion: https://www.railml.org/forum/index.php?t=msg&th=571&start=0& (link to the railML^® website)

Mit Version 2.4 wurde <blocks> als optional zugelassen. Damit soll ermöglicht werden Sonderbelegungen eines Gleises abzubilden. Siehe dazu im Forum: https://www.railml.org/forum/index.php?t=msg&th=571&start=0& (link to the railML^® website)

Open issues / Offene Punkte/Pedenzen / Questions ouvertes

Not yet described. / Noch nicht beschrieben. / Pas encore décrit.