Latest revision as of 18:43, 19 December 2019
Introduction
Documentation
Syntax
|
Documentation
|
TSI category of line as defined in TSI INF section 4.2.1; There should be one code for each type of traffic (passenger, freight) allowed on that line
|
Subschema
|
infrastructure
|
Parents*
|
line
|
Children
|
None
|
Attributes:
- value: TSI category of line as defined in TSI INF section 4.2.1 (optional;
xs:string ; patterns: other:w{2,})
- Possible values:
- F1
- F1520
- F1600
- F2
- F3
- F4
- P1
- P1520
- P1600
- P2
- P3
- P4
- P5
- P6
|
*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.
|
|
Documentation
|
TSI category of line as defined in TSI INF section 4.2.1; There should be one code for each type of traffic (passenger, freight) allowed on that line
|
Subschema
|
infrastructure
|
Parents*
|
line
|
Children
|
None
|
Attributes:
- value: TSI category of line as defined in TSI INF section 4.2.1 (optional;
xs:string ; patterns: other:w{2,})
- Possible values:
- F1600
- F1520
- F4
- F3
- F2
- F1
- P1600
- P1520
- P6
- P5
- P4
- P3
- P2
- P1
|
*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 attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues