| Re: Extension of places and service [message #838 is a reply to message #834] |
Thu, 01 November 2012 13:14   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear all,
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
That model would be:
- simple: Just a sequence of one element with four attributes.
- more flexible: One could assign classes to all type but one does not
need to or can also say "all classes". (One could make the dining car
seats or the sleeping beds or even the WCs for 1st class only...)
The types of "boolean character" such as "mobile service" or "WLAN" do not
need the "numberOf" attribute: They are just named, just enumerated.
The types of "numeral character" such as "seats" or "WCs" can have the
"numberOf" attribute if the number is known.
One could use such types as "restaurant seats" like boolean-style ("There
are restaurant seats but it doesn't matter how many") or with a certain
number. For many usages, it would be enough just to name/enumerate the
types of service without the number of places, namely just to place a
symbol in the passenger information.
Joachim: How about a track ticket?
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
