Generic:weekPatterns

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element Generic:weekPatterns of railML® version 3.3
 
Documentation In order to allow for printing of schedules, this element allows to specify a number of week patterns. These patterns are considered to be the base of the provided bitmask. The leading element in terms of when an operation takes place and when it is not is the bitmask.
Subschema generic
Parents* bitmaskValidity,

periodBitmask

Children weekPattern (1..*)
Attributes:None
*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 Generic:weekPatterns of railML® version 3.2
 
Documentation In order to allow for printing of schedules, this element allows to specify a number of week patterns. These patterns are considered to be the base of the provided bitmask. The leading element in terms of when an operation takes place and when it is not is the bitmask.
Subschema generic
Parents* bitmaskValidity,

periodBitmask

Children weekPattern (1..*)
Attributes:None
*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.


 

This element does not appear in railML® 3.1 within the generic subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.


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.

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues