From railML 3 Wiki
Revision as of 11:56, 14 February 2021 by RailML Coord Documentation (talk | contribs) (1 revision imported: http→https)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Automatic Schemaexport for Element name

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
  • 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),

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.