| Re: new values for places and service [message #1834 is a reply to message #1785] |
Mon, 11 June 2018 15:03   |
Torben Brand
Messages: 158
Registered: March 2016
|
Senior Member |
|
|
Jernbanedirektoratet would like to thank the RS coordinator for his quick feedback and implementation of the suggested values. However this has spurred us to think further about refining the service/places. We would thus like to ask for the following.
Clearer definition of what is a place and what is a service.
We see this issue especially in the toilets (which now are mapped under both elements). As this is on one side a place you can occupy and also it is an extra service to the customers. But for univocity we should choose only one. As both elements have a count attribute both elements can count physical places. Leaving out the count just the type of service is indicated.
We suggest to refine further the definitions in the wiki by adding the following words highlighted in blue:
Places: The element <places> contains the data related to particular passenger planned regular transportation capacity with respect to the various categories of providing space for them.
Service: The element <service> can be used for a list of description of any additional service to the planned regular transportation capacity provided per vehicle. This can be catering, baggage, toilets, low floor portion, conference compartment, internet access etc. The element can also be used to specify particular provisions of a goods compartment.
This would then be in line with what the RS coordinator writes in the forum:
"Please note that values "impairedToilet" and "toilet" are still in tPlaceCategory but are not sensible as "Places". Thus the related values at tServiceType shall be used." I assume this means that they are deprecated. If this is correct please mark them as DEPRECATED in the wiki. Or do you not deprecate enumeration values?
To be consistent with the definition the following <places> @category attribute enumeration values should be moved to <service> @type enumeration value:
"bicycle" - the passenger does not sit on his bicycle while riding the train. He uses either the category attribute enumeration value "standing" or one of the seating classes.
"bistro" and "restaurant" - The passenger has a seat in one of the classes and uses the bistro or restaurant seat additionally to his regular seat while eating. So the seat is an additional service.
It can be discussed for backwards compatibility reasons to keep the attributes in <places>.
Further details on folding seats
There is now a value "foldingSeat". But we would also like to use it in combination with the classes.
As we can not use two enumeration values for the same @category in one <places> element, we need to create a new optional boolean attribute @isFixedSeat. Default value is "true". The value "true" means the seat is a fixed seat. The value "false" means the seat is a folding seat with the same definition as enumeration value "foldingSeat".
Example:
<passenger>
<places category='class3' count='15' isFixedSeat='true'/>
<places category='class3' count='5' isFixedSeat='false'/>
Resulting in 20 seats of category class3.
Further details on standing places
Jernbanedirektoratet needs, for a better detail of capacity planning, to differentiate in the quality levels of standing places (attribute @standing).
We therefore will use the following other: extensions and suggest to adopt it to the enumeration list if other users will use it.
"other:standingCategoryA" - Standing places with possibility to hold on to designated grips. Calculated with 2 passengers per square meter of available passenger standing area ("standingArea") with all seats in use ("class1", "class2" and "class3").
"other:standingCategoryB" - Standing places with calculated with 4 passengers per square meter of available passenger standing area ("standingArea") with seats of "class1" and "class2" in use.
"other:standingCategoryC" - Maximum number of standing places up to the technical or safety level of the vehicle with seats of "class1" and "class2" in use.
Alternative to the two last suggested extensions
Alternatively we could add a new:
<places>@category enumeration value "seat"
<places@class optional attribute with enumeration values "1","2" and "3" or as integer. Alternative the more ambigious @qualityLevel as string.
Mark <places>@category enumeration values "class1", "class2" and "class3" as deprecated.
Then you could freely combine and define the classes/quality level of seats, folding seats and standing places.
Further new enumeration value to places/services
Jernbanedirektoratet will use the following other: extensions and suggest to adopt it to the enumeration list if other users will use it.
"other:stroller" - Number of baby or small child transport vehicles possible to place in the <vehicle>. A stroller must have 80cmx120cm designated area and access from the public entry area and not hinder the through-fare. (Other names: pram, pushchair, buggy. See upcoming glossary)
Depending of how you see the discussion on the placement of @bicycles the attribute will be placed under <places> or <service>.
|
|
|
|
Members
Search
Help
Login
Home
