CO:designator

Documentation

Syntax

Autoexport from the XML-Schema for element CO:designator of railML® version 3.2 UML-visualization of CO
Documentation	External identifier of the project.
Subschema	common
Parents*	areaElementProjection, aspectRelation, assetsForInterlocking, balise, baliseGroup, border, bufferStop, combinedRoute, conflictingRoute, controller, controlsInterface, crossing, crossingInPosition, dangerPoint, derailerIL, derailerIS, derailerInPosition, destinationPoint, detector, detectorInState, electrificationSection, ellipticalProjection, endOfTrack, etcsArea, etcsLevelTransition, formation, freightFacilities, genericDetector, hasAspect, hasDetectorTypes, hasElementGroupType, hasHmiIndication, hasLevelCrossingType, hasOperatorCommand, hasRouteType, hasTVDresetStrategy, implementsElementGroup, infrastructureVisualization, interface, keeper, key, keyLockIL, keyLockIS, keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, linearElementProjection, loadingGauge, localOperationArea, manufacturer, mileageChange, movableBridge, movableCrossing, netElement, operationalPoint, operator, overCrossing, overlap, overlapRelease, owner, permissionZone, places, platform, platformEdge, powerSupplyIL, project, radioBlockCentre, radioBlockCentreBorder, restrictionArea, route, routeActivationSection, routeEntry, routeExit, routeRelation, routeReleaseGroupAhead, routeReleaseGroupRear, routeSequence, routeStatusIndicator, service, serviceSection, shuntingZone, signalBox, signalIL, signalIS, signalIndicator, signalWithAspect, specificInfrastructureManager, speedSection, spotElementProjection, stationIndicator, stoppingPlace, switchIL, switchIS, switchInPosition, track, trackBed, trackGauge, trackIL, trainDetectionElement, trainNumberField, trainProtectionElement, trainRadio, tunnelGateIL, tunnelGateIS, tvdSection, underCrossing, usesSymbol, vehicle, vehiclePart, weightLimit, workZone
Children	None
Attributes: register: name of a register where the designator entry can be found (obligatory; xs:string), entry: the designator of the element in the specified register (obligatory; xs:string), description: description of the designator, which can be used to provide basic information about an external system that uses the designator for external referencing (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:designator of railML® version 3.1 UML-visualization of CO
Documentation	This element is not documented in the schema!
Subschema	common
Parents*	activatedBy, activationCondition, aspectRelatedDelay, aspectRelation, assetsForIL, atpDevice, balise, border, bufferStop, combinedRoute, command, conflictingRoute, controlledInterlocking, controlledSystemAsset, controller, controlsInterface, controlsSystemAsset, controlsTrackAsset, crossing, crossingInPosition, dangerPoint, deactivatedBy, delayBySwitchPosition, derailerIL, derailerIS, derailerInPosition, destinationPoint, detectorInState, distantAspect, electrificationSection, facingSwitchInPosition, genericDetector, givenAspect, givenPosition, givenPosition, givenPosition, givenState, givenState, givenState, hasAspect, hasConfiguration, hasDetectorTypes, hasElementGroupType, hasLevelCrossingType, hasPositionRestriction, hasRouteType, hasTVDresetStrategy, implementsElementGroup, implementsSignalplan, interface, itinerary, key, keyLockIL, keyLockIS, keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, loadingGauge, localOperationArea, masterAspect, message, movableCrossing, operationalPoint, overCrossing, overlap, overlapRelease, permissionZone, platform, powerSupplyIL, reasonForConflict, relatedCrossingAndPosition, relatedDerailerAndPosition, relatedDerailerInPosition, relatedDetectorAndState, relatedLevelCrossingAndState, relatedLockAndState, relatedSectionAndVacancy, relatedSignalAndAspect, relatedSwitchAndPosition, relatedSwitchInPosition, requiredCrossingPosition, requiredDerailerPosition, requiredDetectorState, requiredKeyLockState, requiredLevelCrossingState, requiredSectionState, requiredSignalAspect, requiredSwitchPosition, requiresLevelCrossingInState, requiresSwitchInPosition, restrictionArea, route, routeActivationSection, routeEntry, routeExit, routeRelation, routeReleaseGroupAhead, routeReleaseGroupRear, serviceSection, shuntingZone, signalBox, signalDelayTime, signalIL, signalIS, signalWithAspect, slaveAspect, specificIM, speedSection, stoppingPlace, switchIL, switchIS, switchInPosition, switchPositionInDepartureTrack, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, tvdSection, underCrossing, weightLimit, workZone
Children	None
Attributes: register: name of a register where the designator entry can be found (obligatory; xs:string), entry: the designator of the element in the specified register (obligatory; 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 element documentation has been changed.

The parents have changed.

The attributes have been changed.

Best Practice / Examples

Usage of @register

In principle, @register is defined as a xs:string and can be filled arbitrarily. Please, observe the rules explained under Dev:Registers#Expansion. In brief:

• Registers that appear in codelist registers.xml should be called by the respective code. E.g. register=DB640 for the register of station codes of the Austrian Federal Railways (Dienstbehelf 640).
• Registers that do not appear in registers.xml should be called with a project code starting with an underscore. E.g. register=_SnakeOilCatalogue.
  If the register you are referring to is widely employed, think about contacting us to get it included into the codelist.