The first solution has the advantage that it leaves the operating period element unchanged and thus also the concept of defining the operating days remains clear and simple.
From SBB's point of view, it would be worth considering defining the lock periods outside the IS subschema in RailML 3 with references to the IS elements. The following points would argue in favour of this:
1. locking periods come from operative work. Maintenance and infrastructure planning are separate departments and their data is maintained in separate systems.
2. With the desired possibility of referencing external data (especially for IS data), you could also define blocking periods without also transferring the IS elements.
Best regards
Heribert Neu
SBB AG
Informatik
Haslerstrasse 30, CH-3000 Bern 65
Members
Search
Help
Login
Home
