| stopDescription: Default values for optional attributes [message #1544] |
Fri, 07 April 2017 12:20  |
Philip Wobst
Messages: 47
Registered: November 2013
Location: Hanover, Germany
|
Member |
|
|
The need to define the common defaults for optional attributes were discussed during timetable developer meeting in Berne (23.03.2017). The main issue is whether or not default values can be anticipated when an attribute is missing.
Please provide feedback regarding the following change to the Wiki here in the forum.
The following is a suggested amendment of the Best Practices for TT:stopDescription
Default values for optional attributes
The following attributes are optional for a stopDecription and no default values have been defined in the XSD. The best practice for an exporting system is to provide these attributes for the stopDescription to avoid misinterpretation by the importing system.
However, should this not be the case then following default values can be anticipated (these were reviewed and mutually agreed on at the last TT developer meeting in Berne on the 23rd of March 2017):
- onOff: both
- operationalStopOrdered: false
- stopOnRequest: false
- guaranteedPass: false
- commercial: true
NOTE: In railML 3.X these attributes shall either have an agreed default value in the XSD or they should be made mandatory.
|
|
|
|
Members
Search
Help
Login
Home
