From railML 2 Wiki
Jump to navigation Jump to search

Notes regarding operatingPeriodRef

Philip Wobst 09:08, 16. Dez. 2014 (CET): I do not understand how the following shall be possible via the stopDescription - " can only be used to change between a certain stop and run through but not to switch between two different stop types depending on the days of operation.". How can you create a run through with a fixed ocpType='stop' and arrival < departure - please clarify. --Vasco Paul Kolmorgen 09:24, 16. Dez. 2014 (CET)

Dirk Bräuer 16:07, 16. Dez. 2014 (CET):

Dear Philip, you should ask the person who introduced the attribute "operatingPeriodRef" at <stopDescription>. From my opinion, this attribute is not useful here.

So what can we do with this attribute?

  • If <stopDescription>.operatingPeriodRef refers to the same <operatingPeriod> as the train part does, it would be redundant and therefore could be omitted.
  • If <stopDescription>.operatingPeriodRef refers to the an <operatingPeriod> with more operating days than the train part has, it would be a semantical error: You cannot stop more often than the train operates.
  • If <stopDescription>.operatingPeriodRef refers to the an <operatingPeriod> with less operating days than the train part has, what applies to the other days - i. e. the difference quantity of days when the <trainPart> operates but the <stopDescription> is not valid?

I only wanted to point out that in these cases, the train should be understood as running through. However, I do not want to recommend such a usage: " aware that other given attributes as run times, supplements etc. become incorrect by this practice". It's only that we do have this attribute so we have to clarify what happens if somebody uses it. I would welcome an initiative to declare it obsolete.