RTM:associatedNetElement/3.2

Automatic Schemaexport for Element associatedNetElement

Autoexport from the XML-Schema for element RTM:associatedNetElement of railML® version 3.2 UML-visualization of RTM
Documentation	defines LinearLocation of the path of each track
Subschema	Rtm4railml
Parents*	areaLocation, linearLocation
Children	geometricCoordinateBegin (0..1), geometricCoordinateEnd (0..1), linearCoordinateBegin (0..1), linearCoordinateEnd (0..1)
Attributes: intrinsicCoordBegin: locates beginning of a linear net element in an intrinsic coordinate (optional; xs:double), intrinsicCoordEnd: locates end of a linear net element in an intrinsic coordinate (optional; xs:double), keepsOrientation: As of version 3.2 this attribute is obsolete. It turned out that this attribute although required does not serve any meaningful purpose nor did anyone know what it was supposed to do. It will be removed as of version 3.3 of railML. (obligatory; xs:boolean), netElementRef: reference an object using its UUID or GenericID (xs:ID) (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|\{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}), posBegin: position on a netElement defined as distance from its start regardless the absolute mileage of the beginning of area covered by some functional IS entity (optional; xs:decimal), posEnd: position on a netElement defined as distance from its start regardless the absolute mileage of the end of area covered by some functional IS entity (optional; xs:decimal), sequence: enumerator of an Associated net element in a sequence which defines Linear location. The correct ordering of the list should be checked against the topology definition of the network. (optional; xs:nonNegativeInteger)
*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.