CO:name

From railML 3 Wiki
Revision as of 17:40, 19 December 2019 by RailML Coord Documentation (talk | contribs) (Created page with "{{subst:docBase |element=name |subschema=CO}}")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element CO:name of railML® version 3.2
Documentation This element is not documented in the schema!
Subschema common
Parents* alternative,

announcement, approvedBy, areaElementProjection, balise, baliseGroup, border, bufferStop, category, checkedBy, commercialTrain, concessionaire, contractor, crossesElement, crossing, customer, derailerIS, detector, electrificationSection, elementState, ellipticalProjection, etcsArea, etcsLevelTransition, genericArea, geometricPositioningSystem, geometryPoint, gradientCurve, hasHmiIndication, hasOperatorCommand, holiday, horizontalCurve, infrastructureManager, infrastructureState, infrastructureVisualization, keeper, keyLockIS, levelCrossingIS, line, linearElementProjection, linearPositioningSystem, loadingGauge, manufacturer, mediaCategory, mileageChange, netElement, netRelation, network, networkResource, operationalPoint, operationalTrain, operationalUndertaking, operator, organizationalUnit, overCrossing, owner, passengerTextInfo, phase, platform, platformEdge, project, radioBlockCentreBorder, railwayUndertaking, reserve, restrictionArea, revisedBy, revision, screenPositioningSystem, serviceSection, signalIS, speedProfile, speedSection, spotElementProjection, stoppingPlace, switchIS, timetableScenario, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, transportService, tunnelGateIS, underCrossing, usesSymbol, validity, vehicleManufacturer, vehicleOperator, weightLimit

Children None
Attributes:
  • name: should be interpreted in its elements' context (e.g. signal/name, vehicle/name) (obligatory; xs:string),

  • description: should be interpreted in its elements' context, substantiates the name (optional; xs:string),

*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:name of railML® version 3.1
Documentation This element is not documented in the schema!
Subschema common
Parents* areaElementProjection,

balise, border, bufferStop, concessionaire, contractor, crossesElement, crossing, customer, derailerIS, electrificationSection, elementState, geometricPositioningSystem, geometryPoint, gradientCurve, horizontalCurve, infrastructureManager, infrastructureState, keyLockIS, levelCrossingIS, line, linearElementProjection, linearPositioningSystem, loadingGauge, netElement, netRelation, network, networkResource, operationalPoint, operationalUndertaking, overCrossing, platform, railwayUndertaking, restrictionArea, screenPositioningSystem, serviceSection, signalIS, speedProfile, speedSection, spotElementProjection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, underCrossing, usesSymbol, vehicleManufacturer, vehicleOperator, visualization, weightLimit

Children None
Attributes:
  • name: should be interpreted in its elements' context (e.g. signal/name, vehicle/name) (obligatory; xs:string),

  • description: should be interpreted in its elements' context, substantiates the name (optional; xs:string),

*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.


Changes 3.1→3.2

The parents have changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues