| circulations should be optional [message #912] |
Wed, 02 January 2013 10:29  |
Andreas Tanner
Messages: 52
Registered: March 2012
|
Member |
|
|
Dear group,
currently blocks can be defined only when also at least one circulation
is present: the type rRostering has mandatory child elements blockParts,
blocks and circulations. We use blocks to describe vehicle duties within
a day, and circulations to concatenate them within a multiple day schedule.
Now we have a case where there are no circulations present (as they are
defined only in a later planning stage). I think this should be valid,
and therefore I propose to relax the standard in that point. One way
would be to allow a <blocks> element directly below the <timetable>. I
think this would be more correctly model the situation than just to
allow rosterings without circulations because without circulations,
assigning a block to a rostering would be somewhat arbitrary.
So my suggestion is: insert <blocks> with minOccurs=0 into the sequence
of the <timetable> element.
Best, Andreas.
|
|
|
|
Members
Search
Help
Login
Home
