Add status value "unknown"

Description

The enumeration attribute @status contains values:

• conceptual
• planned
• operational
• disabled
• closed

The enumeration is extendable (otherEnumerationValue).

It is suggested to add a new value "unknown"

Background

This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.

The sub-element belongs to , which is a sub-element of , a high-level element. In railML2.4 is used to indicate the status of an OCP with a further sub-element @status. The value list of the @status attribute is extended by “other:Unknown”.

For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, page 29.

Links

• Forum discussion:
• Torben Brand, 31.08.2017: [https://www.railml.org/forum/index.php?t=msg&th=531&goto=1632&#msg_1632]
• Christian Rahmig, 30.08.2018: [https://www.railml.org/forum/index.php?t=msg&th=591&goto=1933&#msg_1933]
• Christian Rahmig, 09.09.2020: [https://www.railml.org/forum/index.php?t=msg&th=760&start=0&]
• Trac tickets:
• #339 (closed)
• #421
• Wiki documentation:
• IS:state: [https://wiki2.railml.org/wiki/IS:state]

Proposed solution in railML 2.5

There are two options:

• option 1: missing attribute to be interpreted as "information is unknwon"
• option 2: extend @status with new value "unknown"

It shall be clarified in the Wiki documentation that:

• the value of @status must always be understood in the context of the file and its usage
• the value of @status is valid only within a certain railML file and the real status of the infrastructure element cannot be derived from the defined value