| Re: Infrastructure train number [message #1342 is a reply to message #1338] |
Thu, 21 January 2016 16:06   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Andreas,
> Indeed, we cannot use an attribute of the <train> since both commercial
> and operational trains are owned by the train operating company.
I do not agree with that statement. An operational train is a train from
the view of the Infrastructure Manager. Therefore, the trainNumber
attribute of an operational train can contain the train (path) number
("operational train number") of that train.
I do agree (already for a long time) that this issue should be solved
better in 3.0. In my opinion it is part of the "re-factoring".
Best regards,
Dirk.
---
Am 22.12.2015 um 15:24 schrieb Andreas Tanner:
> Dear railML community,
>
> one of our customer needs to keep track of the infrastructure train
> number, aka train path number (Trasse). We model this as a property of
> an operational train section.
>
> Indeed, we cannot use an attribute of the <train> since both commercial
> and operational trains are owned by the train operating company. The
> infrastructure manager's view on trains differs.
>
> As for now, we will make use of a custom attribute at
> <trainPartSequence>. Now railML2.3 is already in preview mode, so
> probably we should discuss this issue for 2.4 or 3.
>
> Best regards, Andreas.
|
|
|
|
Members
Search
Help
Login
Home
