Home » railML newsgroups » railml.timetable » Timetable data elements for railVIVID (Identify the main data elements for for the TT subschem)
Timetable data elements for railVIVID [message #1569] Fri, 12 May 2017 12:24 Go to next message
Philip Wobst is currently offline  Philip Wobst
Messages: 34
Registered: November 2013
Location: Hanover, Germany
Member
The railVIVID tool shall show an element count of all relevant elements in a railML file - TRAC ticket #230. I have created a list of elements that contain the main data for the TT subscheme based on existing example data files. Please note the following:
- parent elements (e.g. ocpsTT or connections) are not included
- sub elements that need to be provided together with a parent (e.g. the trainPartRef for the trainPartSequence) are not necessarily included

Please review the list below and provide feedback if you feel an element is missing.

Timetable masterdata
Element                   XPath expression
category                  //timetable/categories/category
operatingPeriod           //timetable/operatingPeriods/operatingPeriod
operatingDayDeviance      //timetable/operatingPeriods/operatingPeriod/operatingDay/operatingDayDeviance
specialService            //timetable/operatingPeriods/operatingPeriod/specialService
holiday                   //timetable/timetablePeriods/timetablePeriod/holidays/holiday

Train data
Element                   XPath expression
trainPart                 //timetable/trainParts/trainPart
passengerUsage            //timetable/trainParts/trainPart/formationTT/passengerUsage
reservationInfo           //timetable/trainParts/trainPart/formationTT/reservationInfo
ocpTT                     //timetable/trainParts/trainPart/ocpsTT/ocpTT
connection                //timetable/trainParts/trainPart/ocpsTT/ocpTT/connections/connection
sectionTT                 //timetable/trainParts/trainPart/ocpsTT/ocpTT/sectionTT
stopDescription           //timetable/trainParts/trainPart/ocpsTT/ocpTT/stopDescription
times                     //timetable/trainParts/trainPart/ocpsTT/ocpTT/times
organizationalUnitBinding //timetable/trainParts/trainPart/organizationalUnitBinding
train                     //timetable/trains/train
trainPartSequence         //timetable/trains/train/trainPartSequence
brakeUsage                //timetable/trains/train/trainPartSequence/brakeUsage
speedProfileRef           //timetable/trains/train/trainPartSequence/speedProfileRef

Train group data
Element                   XPath expression
trainGroup                //timetable/trainGroups/trainGroup
trainRef                  //timetable/trainGroups/trainGroup/trainRef

Rostering
Element                   XPath expression
blockPart                 //timetable/rosterings/rostering/blockParts/blockPart
block                     //timetable/rosterings/rostering/blocks/block
blockPartSequence         //timetable/rosterings/rostering/blocks/block/blockPartSequence
blockPartRef              //timetable/rosterings/rostering/blocks/block/blockPartSequence/blockPartRef
circulation               //timetable/rosterings/rostering/circulations/circulation

Re: Timetable data elements for railVIVID [message #1571 is a reply to message #1569] Fri, 12 May 2017 12:55 Go to previous messageGo to next message
Joachim.Rubröder is currently offline  Joachim.Rubröder
Messages: 29
Registered: September 2004
Junior Member
I think the list covers the main data for the TT subscheme well.

For completeness I would add:
timetablePeriod //timetable/timetablePeriods/timetablePeriod
formationTT //timetable/trainParts/trainPart/formationTT
Re: Timetable data elements for railVIVID [message #1573 is a reply to message #1571] Thu, 18 May 2017 11:12 Go to previous messageGo to next message
Mićo Mićić is currently offline  Mićo Mićić
Messages: 12
Registered: November 2016
Junior Member
Hi Philip

What's about the element //timetable/trainParts/trainPart/formationTT/equipmentUsage?

Regards,
Mico
Re: Timetable data elements for railVIVID [message #1576 is a reply to message #1569] Thu, 18 May 2017 12:59 Go to previous messageGo to next message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 202
Registered: August 2008
Senior Member
Dear all,

I am sceptical that this approach leads to a practical solution.

From my understanding:
- The aim is to avoid a railML file with only "any-fields" (after a
minimum of <railML>).
- The statistic approach to reach this, which is discussed here, shall
lead to a kind of "cover ratio" of railML in a railML file.

I see the following problems:
- Nobody will know which minimum "cover ratio" will be acceptable.
- It depends on the use case which elements are obligatory and which
are optional. So, this approach conflicts with the concept of use cases.

I personally don't think that this should be solved in an automatic and
statistic way but if you want to follow this approach, I would recommend
to count only this elements which are "common to all use cases". Of
course nobody knows all use cases of the future, but analogously it
means: Relatively view, basic elements only. So most acceptable railML
files will have a high "cover ratio".

The current list, from my opinion, is too much unbalanced by containing
too many special and possibly still not all basic elements.

Best regards,
Dirk.
Re: Timetable data elements for railVIVID [message #1582 is a reply to message #1576] Thu, 18 May 2017 16:07 Go to previous messageGo to next message
Philip Wobst is currently offline  Philip Wobst
Messages: 34
Registered: November 2013
Location: Hanover, Germany
Member
Dear Dirk,

thank you for the feedback you have provided. However, at this point the aim is not to define a 'cover ratio' but rather to focus on the key elements for a TT data file.
As an example I would like to use Joachims example to include the formationTT of the trainPart. As an optional element it is probably important to show whether or not the data includes this data or not - i.e. is the number of trainParts equal to the number of formationTT elements?
Possibly someone will point out that the reservationInfo/booking element of formationTT is a key indicator for a ticketing system and that it should be included as well.
You have also pointed out that it might be helpful to show the number of extension elements in the file - is that correct?
Could you be more specific about 'too many special and possibly still not all basic elements'?

Best regards,

Philip
Re: Timetable data elements for railVIVID [message #1593 is a reply to message #1582] Mon, 29 May 2017 09:18 Go to previous message
Philip Wobst is currently offline  Philip Wobst
Messages: 34
Registered: November 2013
Location: Hanover, Germany
Member
Dear all,

the aim of railVIVID change is to show the user an overview of the number of main elements in the railML file. It is not designed to be a 'cover' ratio for the complete file. For that reason it might make sense to limit this to the first level of the <timetable> element:

  • timetablePeriods
  • operatingPeriods
  • categories
  • annotations
  • trainParts
  • trains
  • trainGroups
  • rosterings

As a result the display in railVIVID would be "timetable: XX of 8 elements used".

BR, Philip
Previous Topic: Referenzierung von ausgefallenen Zügen / Referencing of canceled trains
Goto Forum:
  


Current Time: Mon May 29 17:10:11 CEST 2017