| Re: infrastructure train path: where to put path parameters [message #936 is a reply to message #915] |
Tue, 12 March 2013 19:38   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Andreas,
what do you mean with "path properties"?
For the state of a train (whether it is ordered, published, invoiced...)
currently there is <trainPart>."processStatus". We did not find its
pre-defined values very helpful, so we use a lot of "other:..." values
with it.
I also would have preferred it at <trainPartSequence> rather than at
<trainPart>. But the original intention was to consequently put everything
into <trainParts> as the real "atoms" of trains. And since I am also a
friend of consequence, I did not invent. I think it is not redundancy:
Sometimes we have different operators for two train parts at the same
<trainPartSequence>, e. g. EB and STB run coupled between Erfurt and
Plaue. One could imagine that there are different states of the
<trainParts> even at the same section: One has already payed its invoice
(processStatus="payed"), the other not (processStatus="invoiced,
reminded...") ;-)
A formationRef is already there at <trainPart>. It is a reference to a
vehicle formation.
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
