| Re: Meaning and usage of @shuntingTime [message #1944 is a reply to message #1927] |
Mon, 03 September 2018 12:18   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Heribert,
thank you for your reply. No objections from my side.
> 1. The values in <times> also have a scope: actual,
> calculated, published, scheduled etc.. The shuntingTime as
> attribute of <ocpTT> does not have this scope and the
> assignment would therefore be problematic.
Yes, I agree.
> 4. Since we have very different use cases for data transfer
> with RailML, I would not restrict flexibility at this
> point.
Ok. I agree that the question "what does @shuntingTime mean" can only be answered by a use case.
So far, we can only summarise that we have no known use case and do not know how to use @shuntingTime. So, I would not like to add any example.
However, we still should avoid to have two competing @shuntingTimes. So, there is still my suggestion to declare one or both as deprecated.
At the today's <TT> developer telephone conference, it was agreed to open a "ticket" to fix that at least one @shuntingTimes should become deprecated from a future railML <TT> version.
With best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
