CO:vehicleOperator/3.2: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][checked revision]
(Updated page CO:vehicleOperator/3.2 using XSD2MediaWiki Converter 1.0.6)
(Updated page CO:vehicleOperator/3.2 using XSD2MediaWiki Converter 1.1.1)
Line 4: Line 4:
|subschema=common
|subschema=common
|subschema_slug=CO
|subschema_slug=CO
|documentation=DEPRECATED with railML 3.2; use organizationalUnit instead;
|documentation=DEPRECATED with railML 3.2; use organizationalUnit instead;<br>Some kind of subcontractor (railway undertaking) that operates the vehicle, if different from the one that is responsible for the commercial service
Some kind of subcontractor (railway undertaking) that operates the vehicle, if different from the one that is responsible for the commercial service
|version=3.2
|version=3.2
|parent={{parent|subschema=CO|name=organizationalUnits}}
|parent={{parent|subschema=CO|name=organizationalUnits}}

Revision as of 10:53, 26 April 2023

Automatic Schemaexport for Element vehicleOperator

Autoexport from the XML-Schema for element CO:vehicleOperator of railML® version 3.2
Documentation DEPRECATED with railML 3.2; use organizationalUnit instead;
Some kind of subcontractor (railway undertaking) that operates the vehicle, if different from the one that is responsible for the commercial service
Subschema common
Parents* organizationalUnits
Children isConcessionaire (0..1), isContractor (0..1), isCustomer (0..1), isInfrastructureManager (0..1), isOperationalUndertaking (0..1), isRailwayUndertaking (0..1), isVehicleManufacturer (0..1), isVehicleOperator (0..1), isVehicleOwner (0..1), name (0..*)
Attributes:
  • code: insert here the matching code from the relevant codelist (optional; xs:string),

  • id: unique identifier (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|\{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}); compare: Dev:Identities
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.