| Re: [railML 2.5] state [message #2551 is a reply to message #2549] |
Fri, 09 October 2020 15:58   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Hi Christian,
option 2, please.
Option 1 would mean that you change the default value (meaning) of <state>. So far, there was no "unknown" documented. So, we export infrastructure without <state> when we mean "operational" - we simply do not repeat the "operational" at all possible occurrences. Rather, we switch them off (with "disabled") in the (rare) case we haven an element which cannot be used. If you now define the default value as "unknown", all our existing railML files would immediately change their meaning from "operational" to "unknown".
I also want to remind here that "operational" or "unknown" cannot mean the actual state of the element; rather, they must be understood in the context of the certain railML file where they occur. Therefore, "operational" means: Used in the context in this railML file, or assumed to be operational here. No guarantee, no deduction allowed outside the railML file. It can be an element which is not even built jet, a proposed station for instance.
So to encode an element which is "unknown" is an even more rare and a bit strange case from our view. Of course all elements which are _not_ included in the railML file at all can be obviously unknown to the creator of that file.
With best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
