| Re: Extension of places and service [message #855 is a reply to message #838] |
Wed, 07 November 2012 23:30   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
> since it is clear where Andreas' remarks lead to: How about the
> following suggestion for RailML 3.0:
>
> - Unification of <passengerUsage>.<service> and
> <passengerUsage>.<places> - no determination between them, just
> "passengerUsage".
>
> - "Type" as an attribute, enumeration of all known services and
> places: Seats, folding seats, beds, WC, WLAN, mobile service... etc.
>
> - Optional attribute independent from "type": class = enumeration of
> (1st, 2nd, 3rd, all, unknown...)
>
> - Optional attribute independent from "type": reservation =
> enumeration of (notPossible, possible, recommended, compulsory)
>
> - Optional attribute independent from "type": numberOf = integer
Filed a Trac ticket for this issue:
http://trac.assembla.com/railML/ticket/186
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
