CO:vehicleManufacturer

Introduction

Autoexport from the XML-Schema for element CO:vehicleManufacturer of railML^® version 3.2 UML-visualization of CO
Documentation	DEPRECATED with railML 3.2; use organizationalUnit instead; The vehicle manufacturer produces the railway vehicles.
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}\})
^*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.

Autoexport from the XML-Schema for element CO:vehicleManufacturer of railML^® version 3.1 UML-visualization of CO
Documentation	This element is not documented in the schema!
Subschema	common
Parents^*	organizationalUnits
Children	name (0..*)
Attributes: code: insert here the matching code from the relevant codelist (optional; `xs:string`), id: unique identifier (optional; `xs:ID`; 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}\})
^*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.

The element documentation has been changed.

The children have changed.

The attributes have been changed.