RS:operator

operator
 

Scheme description / Schemenbeschreibung / Description du schéma

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

• Parent: <classification>

• Children: <vehicleIdentification> (introduced with version 2.3)

Multiplicity / Anzahl / Multiplicité

[0..∞]

Semantics / Bedeutung / Sémantique

The element <operator> contains all data an vehicle operator typically uses for identification and management of its vehicles. It is possible to have several operators listed for one vehicle.

Das Element <operator> enthält alle Daten des Betreibers für die Identifizierung und Verwaltung. Es besteht die Möglichkeit, dem Fahrzeug mehrere Betreiber zuzordnen.
 
Please, be aware of the semantic constraint(s)!

Attributes of operator / Attribute von operator / Attributs de operator

• operatorClass: This is the class number or identification the operator has given to this vehicle.
• operatorName (deprecated with version 2.2): This is the name of the operator at the time of using this vehicle.
• vehicleOperatorRef (introduced with version 2.2): Reference to a common list of <vehicleOperator>s. It shall be used in preference to operatorName.
• startDate: This is the begin of validity period of operator data for this vehicle, i.e. the period when the vehicle was used by that operator. Please, recognize the semantic constraint.
• endDate: This is the end of validity period of operator data for this vehicle, i.e. the period when the vehicle was used by that operator. Please, recognize the semantic constraint.

Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques

• operatorClass: xs:string (external link), mandatory
• operatorName: xs:string (external link), optional
• vehicleOperatorRef: xs:IDREF (external link), optional
• startDate: xs:date (external link), optional; shall be lower or equal endDate if both are used.
• endDate: xs:date (external link), optional; shall be higher or equal endDate if both are used.

With the startDate and endDate attributes the validity of the operator data is limited to the given time period. Thus the relation between the vehicle and operator can be unique for any particular date.

Semantic Constraints / Semantische Beschränkungen / Contraintes semantiques

Semantic Constraint "TT:001": Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other validity periods. Proposed on November 12th 2018 Approved on March 21st 2019 FIXME: add Link to discussion! Please, recognize our guidelines on semantic constraints

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

<metadata>
  <organizationalUnits>
    <vehicleOperator id='vop_1' name='NSB'/>
    <vehicleOperator id='vop_2' name='DB'/>
    <vehicleManufacturer id='vm_3' name='Siemens Verkehrstechnik'/>
  </organizationalUnits>
</metadata>

<!-- ... -->

<vehicle id='veh_123' axleSequence='Co&apos;Co&apos; de' numberDrivenAxles='6' length='20.960' speed='160' bruttoWeight='122' nettoAdhesionWeight='122'>
  <classification>
    <manufacturer vehicleManufacturerRef='vm_3' manufacturer-Type='ME26'/>
    <operator vehicleOperatorRef='vop_1' operatorClass='Di6'/>
    <operator vehicleOperatorRef='vop_2' operatorClass='251'/>
  </classification>
</vehicle>

Notes / Anmerkungen / Notes

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

Open issues / Offene Punkte/Pedenzen / Questions ouvertes

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