CO:elementState

From railML 3 Wiki
Revision as of 16:39, 30 October 2024 by RailML Bot XSD2MediaWiki (talk | contribs) (Created page CO:elementState using XSD2MediaWiki Converter 1.1.1)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element CO:elementState of railML® version 3.3
    
Documentation Allows specifying states deviating from the ones specified under //common/states. This is useful for defining elements that will be put into or out of operation while other parts of the resources described in this document stay in the same state, e.g. construction of a new bridge or level crossing.
Subschema common
Parents*

aspectRelation, assetsForInterlocking, balise, baliseGroup, border, bufferStop, combinedRoute, conflictingRoute, controller, controlsInterface, crossing, crossingInPosition, dangerArea, dangerPoint, derailerIL, derailerIS, derailerInPosition, destinationPoint, detector, detectorInState, electrificationSection, emergencyStopArea, endOfTrack, etcsArea, etcsLevelTransition, formation, genericArea, genericDetector, hasAspect, hasDetectorTypes, hasElementGroupType, hasHmiIndication, hasLevelCrossingType, hasOperatorCommand, hasRouteType, hasSignalLamp, hasTVDresetStrategy, implementsElementGroup, interface, key, keyLockIL, keyLockIS, keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, linesideElectronicUnitIL, linesideElectronicUnitIS, loadingGauge, localOperationArea, loop, mileageChange, movableBridge, movableCrossing, objectController, operationalPoint, overCrossing, overlap, overlapRelease, permissionZone, platform, platformEdge, powerSupplyIL, radioBlockCentre, radioBlockCentreBorder, restrictionArea, route, routeActivationSection, routeEntry, routeExit, routeRelation, routeReleaseGroupAhead, routeReleaseGroupRear, routeSequence, routeStatusIndicator, serviceSection, shuntingZone, signalBox, signalIL, signalIS, signalIndicator, signalWithAspect, specificInfrastructureManager, speedSection, stationIndicator, stoppingPlace, switchIL, switchIS, switchInPosition, track, trackBed, trackGauge, trackIL, trainDetectionElement, trainNumberField, trainProtectionElement, trainRadio, tunnelGateIL, tunnelGateIS, tvdSection, underCrossing, vehicle, vehiclePart, weightLimit, workZone

Children

name (0..*), validity (0..*)

Attributes:
Possible values:
  • closed: The element is no longer available for operation. Usually a planning phase is needed before reopening the element for operation again. Otherwise a closed element could also be dismantled.
  • conceptual: The construction or commissioning of the element is planned for the medium or long term. However, there are still no concrete (planning) activities for the construction of the element beyond the preliminary planning and cost estimation.
  • disabled: The element is currently not usable, switched off or deactivated and therefore cannot be used regularly. However, it can be put back into operation at short notice without further construction, acceptance or approval activities.
  • dismantled: The element has been dismantled and is no longer available for use. In order to get it back into operation, planning needs to be conducted again.
  • operational: The element is operational and can be used regularly.
  • planned: The construction or commissioning of the element is planned concretely and at short notice or concrete planning activities for the construction take place, e.g. design, approval or implementation planning, cost calculation, award of contracts. It is not normally possible to use the element.
  • withdrawn: Planning for the element was withdrawn without building it. Planning could continue at any time in the future. It is not possible to use the element (in this configuration) for operation.
*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.


 

This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.
This element does not appear in railML® 3.1 within the CO subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.


Changes 3.2→3.3

There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
Introduced with version 3.3.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues