Home » railML newsgroups » railml.timetable » Additional commercial attributes from TAP TSI for timetables
Re: Additional commercial attributes from TAP TSI for timetables [message #1305 is a reply to message #1300] Wed, 14 October 2015 18:36 Go to previous messageGo to previous message
Stefan Jugelt is currently offline  Stefan Jugelt
Messages: 3
Registered: May 2014
Junior Member
Dear all,

Philip Wobst wrote:
>
> Dear all,
>
> @Stefan: Thank you for the example file for further discussion. I do
> have some questions/feedback:
>
> 1. additional attribute for 2.3
> I believe the agreement of our meeting was to create a new and TSI
> specific attribute - e.g. 'tapTsiCode' - so that the original railML 2.2
> data representation is not affected. See #2 for sample.
>

Philip you are right, the agreement was to use a new TAP TSI specific
attribute for railML and not to change the enumeration "category" in
railML.

> 2. Use of the number and not string code
> Should we actually use a string as a code or should we use the actual
> number value of the code? I would suggest to use the actual number code
> value instead of a string because the code could be interpreted directly
> if the default TAP TSI codes are used. Furthermore, it would allow for
> at least a limited amount of verification - i.e. number from 1 to 999 as
> a valid code reference instead of any string. A set of default mapping
> for the existing railML enumeration categories could be provided in the
> Wiki.
>

I would suggest to use numeric values for the tapTsiCode-attribute. A
restruiction to up to 999 entries is more than enough. I f we agree to
this approach I would provide the mapping TAP TSI <--> railML.

> <formationTT>
> <passengerUsage>
> <!-- 100 seats in 1st class -->
> <places category="class1" tapTsiCode="4" count="100"/>
> <!-- 300 seats in 2nd class -->
> <places category="class2" tapTsiCode="5" count="300"/>
> <!-- Snack trolley available -->
> <service name="trolley" tapTsiCode="25" count="1"/>
> </passengerUsage>
> /formationTT>
>

The proposal is OK. The numbers reflect the current usage of these entries
in the TAP TSI.

> 3. Documentation and versions
> For me it is still not clear where the code list is 'published' and how
> different versions can be managed between a railML provider and consumer.
> Within the railML release there should be a codelist-schema xsd for the
> file but the actual code list. It would then be up to the
> provider/consumer to agree on an actual code list version - either
> online or provided within their interface process.


The website with the actual version of the TAP TSI:
http://www.era.europa.eu/Document-Register/Pages/TAP-TSI.asp x . The code
lists will be available soon as XML-file on this website. We are waitung
for the final approval.

Kind regards,

Stefan Jugelt




--
----== posted via PHP Headliner ==----
 
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:
  


Current Time: Sun Apr 28 19:46:52 CEST 2024