IS:operationalPoint/3.3

Automatic Schemaexport for Element operationalPoint

Autoexport from the XML-Schema for element IS:operationalPoint of railML® version 3.3      UML-visualization of IS
Description	point in the railway network that is essential for railway operation. Typical examples for railway operational points are stations, block signals or stopping points. Operational points allow an interaction between the railway operator and the train driver.
Subschema	infrastructure
Parents*	operationalPoints
Children	name (0..*), isValid (0..*), areaLocation (0..*), linearLocation (0..*), spotLocation (0..*), gmlLocation (0..*), networkLocation (0..*), designator (0..*), typeDesignator (0..*), elementState (0..*), infrastructureManagerRef (0..*), connectedToLine (0..*), limitedByBorder (0..*), opEquipment (0..1), opOperations (0..1)
Attributes: basedOnTemplate: references a generic operational point (optional: tRef : xs:IDREF), belongsToParent: references the one and only parent operational point of this operational point - if some information exists in parent and child, then information in child overwrites it in parent - if some information exists only in parent, then child inherits this information from parent (optional: tRef : xs:IDREF), timezone: the time zone of the operational point as defined in the time zone database, e.g. "Europe/Berlin" (optional: xs:string : xs:string), id: the file-internal ID of the object (obligatory: tID : xs:ID): compare: Dev:Identities
*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.