Home » railML newsgroups » railml.timetable » [railML3] Unclassified Rostering Blocks
[railML3] Unclassified Rostering Blocks [message #3474] Wed, 19 February 2025 08:29 Go to next message
David Lichti is currently offline  David Lichti
Messages: 54
Registered: December 2020
Member
Dear Community,

We are currently investigating the possibility of a railML export of rollingstock rostering data. One issue with the current railML model of rosterings is that all (stationary) blocks must necessarily be classified into one of the well-known categories [1]. But this may not always be possible, since our system allows the user to plan arbitrary activities with user-defined or no type at all. As I see it, the current rostering model of railML 3.3 does not allow to represent such a block.

We suggest to add a generic <activity> element to the xs:choice of block tasks. Even without a fixed classification, the receiver would still be able to recognize it as a planned activity with a location and start and end times. In any case, the name of the block could give an indication to the human reader, what that block is about.
<block id="bk-3">
  <name name="some very special activity" language="en"/>
  <activity startTime="10:00:00" endTime="14:00:00">
    <location opRef="op-3"/>
  </activity>
</block>

[1] https://wiki3.railml.org/wiki/TT:block#3.3-0

Report message to a moderator

Re: [railML3] Unclassified Rostering Blocks [message #3479 is a reply to message #3474] Mon, 24 February 2025 09:20 Go to previous messageGo to next message
Milan Wölke is currently offline  Milan Wölke
Messages: 213
Registered: April 2007
Senior Member
Hi David,

thanks for your suggestion. We can discuss this, sounds reasonable. I'll put it on the agenda of the next timetable developer meeting.

Is there anyone else in the community interested in this?

Best regards, Milan

Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Re: [railML3] Unclassified Rostering Blocks [message #3503 is a reply to message #3479] Mon, 10 March 2025 11:26 Go to previous messageGo to next message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 80
Registered: March 2015
Member
Hello,

I agree with David's suggestion. If I remember correctly, we had already discussed something similar during the development of the LTCP usecase. However, I think it is important that this new element is not interpreted as an alternative or replacement for the existing 'block' types. I would therefore prefer a somewhat more specific name such as 'reserved' or similar, which in my opinion fits better into the existing list of types.

Best regards
Christian

Report message to a moderator

Re: [railML3] Unclassified Rostering Blocks [message #3672 is a reply to message #3503] Tue, 22 July 2025 12:09 Go to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 213
Registered: April 2007
Senior Member
Hi all,
We added a new type of task, called reserved to be introduced in railML 3.4.

Best regards, Milan

Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Previous Topic: [railML3] Freight facilities of mixed freight trains
Next Topic: [railML2] New semantic constraint for <trainPart>
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon Feb 09 10:25:21 CET 2026