CO:speedProfile

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element CO:speedProfile of railML® version 3.2
Documentation Schema documentation missing!
Subschema common
Parents* speedProfiles
Children braking (0..1), load (0..1), name (0..*), tilting (0..1), trainType (0..*)
Attributes:
  • isBasicSpeedProfile: boolean flag to identify basic speed profiles;
    if NO, then further information need to be defined, e.g. trainType, braking or maxCantDeficiency (optional; xs:boolean),

  • influence: Schema documentation missing! (optional; xs:string)
Possible values:
  • decreasing
  • increasing,

  • maxCantDeficiency: the maximum cant deficiency provided in mm (80..300) (optional; xs:integer; minInclusive: 80; maxInclusive: 300),

  • id: unique identifier (optional; 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}\})
*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 CO:speedProfile of railML® version 3.1
Documentation Schema documentation missing!
Subschema common
Parents* speedProfiles
Children braking (0..1), load (0..1), name (0..*), tilting (0..1), trainType (0..1)
Attributes:
  • influence: Schema documentation missing! (optional; xs:string)
Possible values:
  • increasing
  • decreasing,

  • id: unique identifier (optional; 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}\})
*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.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues