Home » railML newsgroups » railml.timetable » Additional commercial attributes from TAP TSI for timetables
Re: Additional commercial attributes from TAP TSI for timetables [message #1299 is a reply to message #964] Mon, 21 September 2015 18:02 Go to previous messageGo to previous message
Stefan Jugelt is currently offline  Stefan Jugelt
Messages: 3
Registered: May 2014
Junior Member
Dear all,

as agreed during our railml timetable meeting last week I have created for
the proposed attribues one example for the coding of places and services
for a train part:

Example:
<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSpy v2015 sp2
(http://www.altova.com)-->
<railml xmlns="http://www.railml.org/schemas/2013"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.railml.org/schemas/2013 railML.xsd">
<metadata>
<organizationalUnits>
<railwayUndertaking id="CompanyCode_1080" code="1080"/>
</organizationalUnits>
</metadata>
<infrastructure id="inf-0815">
<operationControlPoints>
<ocp id="enee_8010085">
<designator entry="8010085" register="ENEE"/>
</ocp>
<ocp id="enee_8010205">
<designator entry="8010205" register="ENEE"/>
</ocp>
</operationControlPoints>
</infrastructure>
<timetable id="tt-0815">
<trainParts>
<trainPart id="TrainPart-0815-1">
<formationTT>
<passengerUsage>
<!-- 100 seats in 1st class -->
<places category="seatingFirstClass" count="100"/>
<!-- 300 seats in 2nd class -->
<places category="seatingSecondClass" count="300"/>
<!-- Snack trolley available -->
<service name="trolley" count="1"/>
</passengerUsage>
</formationTT>
<ocpsTT>
<ocpTT ocpRef="enee_8010085" ocpType="begin"/>
<ocpTT ocpRef="enee_8010205" ocpType="end"/>
</ocpsTT>
<organizationalUnitBinding>
<railwayUndertaking ref="CompanyCode_1080"/>
</organizationalUnitBinding>
</trainPart>
</trainParts>
</timetable>
</railml>

Some further explanations:
1. The code values for the rail:places/@category shall be stored in an
external code list, not in an enumeration in railML.
2. The code values are available in the files "Codelist_B.4.7161.xml"
(servies) and "Codelist_B.4.9039.xml" (places).
3. The enumeration for the accomodation classes in "tPlaceCategory" and
"tServces" are not needed anymore.

Please check the example and provide your comments.

Kind regards,

Stefan Jugelt

--
----== posted via PHP Headliner ==----

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Connections to external trains
Next Topic: Protocol developer meeting 22nd January 2016 at PSI
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun May 05 06:32:52 CEST 2024