CO:external

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

This element does not appear in railML® 3.3 within the CO subschema. It is available only in railML® 3.1.
There exists an element <generic:external> that might have replaced or preceded it. Do not hesitate to contact railML.org for further questions.

This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1.
There exists an element <generic:external> that might have replaced or preceded it. Do not hesitate to contact railML.org for further questions.

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

border, bufferStop, crossing, derailerIS, electrificationSection, keyLockIS, levelCrossingIS, line, loadingGauge, operationalPoint, overCrossing, platform, restrictionArea, serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, underCrossing, weightLimit

Children None
Attributes:
  • id: an external identifier of the element (optional; xs:string); compare: Dev:Identities,

  • ref: a reference to an external element (optional; xs:string),

  • description: description of the external identifier or reference, providing basic information about external system (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

There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.

Removed with version 3.2. There exists an element <generic:external> that might have replaced it.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues