RTM:level

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element RTM:level of railML® version 3.2
Documentation network view in a sense of aggregation
Subschema Rtm4railml
Parents* network
Children networkResource (0..*)
Attributes:
  • descriptionLevel: This attribute is not documented in the schema! (optional; xs:string)
Possible values:
  • Macro
  • Meso
  • Micro,

  • id: the identifier of the object; this can be either of type xs:ID or UUID (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}}); 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.

Autoexport from the XML-Schema for element RTM:level of railML® version 3.1
Documentation This element is not documented in the schema!
Subschema Rtm4railml
Parents* network
Children networkResource (0..*)
Attributes:
  • descriptionLevel: This attribute is not documented in the schema! (optional; xs:string)
Possible values:
  • Micro
  • Meso
  • Macro,

  • id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; xs:ID; 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}}); 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.


Changes 3.1→3.2

The element documentation has been changed.

The children have changed.

The attributes have been changed.

Semantics

Best Practice / Examples

usually net elements of microscopic level of aggregation are covered by railway tracks.


Additional Information

Notes

Open Issues