RS:operator: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
m (added child vehicleIdentification)
No edit summary
Line 31: Line 31:
* {{Attr|vehicleOperatorRef}} {{RailMLType|tGenericRef}}, optional
* {{Attr|vehicleOperatorRef}} {{RailMLType|tGenericRef}}, optional


* {{Attr|startDate}} {{XsdType|date}}, optional
* {{Attr|startDate}} {{XsdType|date}}, optional; shall be lower or equal {{Attr|endDate}} if both are used.


* {{Attr|endDate}} {{XsdType|date}}, optional
* {{Attr|endDate}} {{XsdType|date}}, optional; shall be higher or equal {{Attr|endDate}} if both are used.


With the {{attr|startDate}} and {{attr|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.
With the {{attr|startDate}} and {{attr|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.

Revision as of 14:54, 22 May 2018


operator
 


Scheme description / Schemenbeschreibung

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

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

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.

Attributes of operator / Attribute von 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 vehicle operators (TOC). 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.
  • 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.

Syntactic Constraints / Syntaktische Beschränkungen

  • startDate xs:date, optional; shall be lower or equal endDate if both are used.
  • endDate xs:date, 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.

Best practice & Examples / Empfohlene Anwendung & Beispiele

<vehicle id='veh_ME26' axleSequence='Co&apos;Co&apos; de' numberDrivenAxles='6' length='20.960' speed='160' bruttoWeight='122' nettoAdhesionWeight='122'>
  <classification>
    <manufacturer manufacturerName='Siemens Verkehrstechnik' manufacturer-Type='ME26'/>
    <operator operatorName='NSB' operatorClass='Di6' startDate='1995-01-01' endDate='1999-01-31'/>
    <operator operatorName='DB' operatorClass='251'/>
  </classification>
</vehicle>

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.