| Re: new values for places and service [message #1785 is a reply to message #1757] |
Thu, 03 May 2018 09:03   |
Joerg von Lingen
Messages: 148
Registered: May 2011
|
Senior Member |
|
|
Some of the suggested values were already available in tPlaceCategory or tServiceType. I have extended the enumerations
by some additional values as suggested. 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.
<xs:simpleType name="tPlaceCategory">
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="class1" />
<xs:enumeration value="class2" />
<xs:enumeration value="class3" />
<xs:enumeration value="standing" />
<xs:enumeration value="standingArea" />
<xs:enumeration value="wheelchair" />
<xs:enumeration value="bicycle" />
<xs:enumeration value="couchette" />
<xs:enumeration value="bed" />
<xs:enumeration value="chair" />
<xs:enumeration value="bistro" />
<xs:enumeration value="restaurant" />
<xs:enumeration value="foldingSeat" />
<xs:enumeration value="impairedToilet" />
<xs:enumeration value="toilet" />
<xs:enumeration value="business" />
<xs:enumeration value="businessCompartment" />
<xs:enumeration value="family" />
<xs:enumeration value="familyCompartment" />
<xs:enumeration value="toddler" />
<xs:enumeration value="toddlerCompartment" />
<xs:enumeration value="sleepingCompartment" />
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="rail:tOtherEnumerationValue" />
</xs:simpleType>
</xs:union>
</xs:simpleType>
<xs:simpleType name="tServiceType">
<xs:annotation>
<xs:documentation>list of common service types</xs:documentation>
</xs:annotation>
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="mobileCatering" />
<xs:enumeration value="WLAN" />
<xs:enumeration value="wheelchairLift" />
<xs:enumeration value="toiletClosed" />
<xs:enumeration value="toiletOpen" />
<xs:enumeration value="toiletHc" />
<xs:enumeration value="Snack" />
<xs:enumeration value="SelfService" />
<xs:enumeration value="PIS" />
<xs:enumeration value="HVAC" />
<xs:enumeration value="APC" />
<xs:enumeration value="SecurityCamera" />
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="rail:tOtherEnumerationValue" />
</xs:simpleType>
</xs:union>
</xs:simpleType>
Joerg von Lingen wrote on 09.04.2018 16:23:
> Thanks for your input. The additional attributes will be probably interesting
> for other users as well. I will look for a good way to incorporate them into the
> existing elements.
>
> Best regards,
> Joerg v. Lingen
>
> Rollingstock Coordinator
>
> On 05.04.2018 16:33, Torben Brand wrote:
>> We need to define the following undefined values in the
>> railML rolling stock schema for the use case capacity
>> planning.
>>
>> The norwegian sector will use the already defined values in
>> railML 2.3 in the wiki under <places> and <service>. We
>> will also define the following "other:" values:
>>
>> Suggestion towards definition of <places> and <service> We
>> define places as capacity of the vehicle. So a 1. class seat
>> or a bed is a place, but a toilet, a seat in the restaurant
>> car is a service as this is used in addition to a place.
>> <places>@category=
>>
>> As the Forum does not support tables I had to restructure
>> the list accordingly:
>> railML value
>> English short definition
>> Norwegian name
>> Comment
>>
>> class1
>> Seating capacity of the vehicle, class1/comfort class
>> Sitteplasser komfort/1.klasse
>>
>> class2
>> Seating capacity of the vehicle, class2/standard
>> Sitteplasser standard/2.klasse
>>
>> standing
>> Number of people capacity of the vehicle, standing
>> Ståplasser, antall. Klappseter i bruk
>>
>> other:standingArea
>> capacity of the vehicle, standing room in square meters.
>> Flip-up seats not in use.
>> Ståplassareal, klappseter ikke i bruk
>> Use <place> for now. Should be moved to an element
>> describing technical characteristics of the
>> <wagon/passanger> later.
>>
>> other:folding
>> Flip-up seats (folding and resting). Folding seats are seats
>> with dedicated area for the seat when it is folded down.
>> Resting seats are in dedicated standing area (like
>> entry/exit area)
>> Klappseter (folde og klapp)
>> We do not differentiate between folding and resting seats
>> here.
>>
>> wheelchair
>> Dedicated place(s) for wheelchair(s)
>> Rullestolplasser
>>
>> bicycle
>> Dedicated place(s) for bicyle(s)
>> Sykkelplasser
>> Use <place> for now, as already defined there. Should be
>> moved to <service> to be conform to definition?
>>
>> bed
>> Number of bed (s). Not differentiated in class.
>> Soveplasser
>>
>> other:sleepingCompartment
>> Number of sleeping compartments. Not differentiated in
>> class.
>> Sovekupeer
>> TAF/TAP differentiates in class of compartment and number of
>> beds in the compartment. Should be grouped somehow later.
>>
>> other:family
>> capacity of seats in the vehicle in family compartment with
>> family services like playroom and baby wagon storage
>> area/places. Services not defined.
>> Famileavdeling, antall sitteplasser
>>
>> other:restaurant
>> Seating capacity in the restaurant/dining car
>> Resturant (antall sitte plasser)
>> Use <place> for now. Should be moved to <service> to be
>> conform to definition?
>>
>>
>> <service>@name=
>>
>> other:wheelchairLift
>> Onboard Wheelchair lift
>> Rullestolheis
>> Separate code list for PRM in TAF/TAP. But this does not
>> contain onboard wheel chair lift.
>>
>> other:toiletClosed
>> toilet with closed sewer system
>> Toalett (lukket system)
>> Should be grouped later. Did not find any code list for
>> toilets in TAF/TAP?
>>
>> other:toiletOpen
>> toilet with open sewer system
>> Toalett (lukket system)
>>
>> other:toiletHc
>> toilet for impaired passengers
>> Toalett (lukket system)
>>
>> other:Snack
>> Kiosk (no seating)
>> Betjent kiosk
>>
>> other:SelfService
>> Food/drink vending machines
>> Automat
>>
>> other:PIS
>> Passenger information system
>> Informasjonssystem
>> Count:"1"=yes, Count:"0"=no or no value. Should be moved to
>> an element describing technical characteristics of the
>> <wagon/passanger> with bolean value later.
>>
>> other:WLAN
>> WLAN/WiFi
>> WiFi
>> Count:"1"=yes, Count:"0"=no or no value. Should be moved to
>> an element describing technical characteristics of the
>> <wagon/passanger> with bolean value later.
>>
>> other:HVAC
>> Heating, Ventilation and Air Conditioning
>> HVAC for passasjerer
>> Count:"1"=yes, Count:"0"=no or no value. Should be moved to
>> an element describing technical characteristics of the
>> <wagon/passanger> with bolean value later.
>>
>> other:APC
>> Automatic passenger counting system
>> APC
>> Count:"1"=yes, Count:"0"=no or no value. Should be moved to
>> an element describing technical characteristics of the
>> <wagon/passanger> with bolean value later.
>>
>> other:SecurityCamera
>> Security camera
>> Trygghetskamera
>> Count:"1"=yes, Count:"0"=no or no value. Should be moved to
>> an element describing technical characteristics of the
>> <wagon/passanger> with bolean value later.
>>
>> As <places> leans towards TSI TAF/TAP code list 9039 and
>> service towards code list 7161 we have tried to use the
>> existing name where they exist and seem logical. But we
>> reccomnd a later through meeting to go through a logical
>> structure of places and service as the definitions in railML
>> and the TAF/TAP seems somewhat incoherrent.
>>
|
|
|
|
Members
Search
Help
Login
Home
