Restructuring of 'passengerUsage'
As suggested in the forum by Dirk Bräuer (1) the may be restructured in the following way:
- Unification of passengerUsage/service and passengerUsage/places into
- category attribute as an enumeration of all known services and places: Seats, folding seats, beds, WC, WLAN, mobile service...
- class attribute as an enumeration of 1st, 2nd, 3rd, all, unknown...
- reservation attribute as an enumeration of notPossible, possible, recommended, compulsory
- count attribute as an integer
One could make the dining car seats or the sleeping beds or even the WCs for 1st class only...
One could use such types as "restaurant seats" like boolean-style (without the 'count' attribute): "There are restaurant seats but it doesn't matter how many" or with a certain number.
This enhancement has influences in the Timetable and Rollingstock sub-schemas.