Home » railML newsgroups » railml.timetable » Different representations of a train
Different representations of a train [message #950] Tue, 19 November 2013 09:49 Go to previous message
Philip Wobst is currently offline  Philip Wobst
Messages: 47
Registered: November 2013
Location: Hanover, Germany
Member
Hi all,

I would like to start a discussion on this topic and I have found two
topics started by Andreas Tanner, IVU with similar content:

train uniqueness constraint II
http://www.railml.org/forum/ro/index.php?group=2&offset= 0&thread=109&id=391

problems with s: uniqueness constraints, scope
http://www.railml.org/forum/ro/index.php?group=2&offset= 0&thread=101&id=360


However, I would like to have a representation of two identical trains
that shows the origin of the train which cannot be represented by the
processStatus of a train (or trainPart). One of the use cases is a view
of a train in a bid/offer process and this would include two, three or
even more 'variants' of the same train.

For this reason we need additional information regarding the source of a
train/trainPart and the following approaches were found. These
approaches do not solve the problem of modeling a bid/offer process in
railML although it would be nice to find a solution that would be
suitable to support this in the future:

1. Create one file for each source
2. Create one timetablePeriod element for each source
3. Use a special trainGroup to identify the trains for one source

With 2 & 3 the constraint for a train could be extended to include the
referenced element - e.g. trainNumber, scope and additionalTrainNumber
have to be unique for each trainGroup.

These solutions are based on existing elements and I would be happy to
get some feedback regarding your views and possibly suggestions on a
meanigful extension that might make it into railML 3.0 to support this.

Kind regards,

Philip Wobst

--
Consultant
Planning and Dispatching Systems
HaCon Ingenieurgesellschaft mbH
Lister Str. 15
30163 Hannover
Germany/Deutschland

Tel. +49 511 33699-498
Fax. +49 511 33699-99
mailto: philipwobst(at)haconde
http://www.hacon.de

railML Partnerlink:
http://www.railml.org//index.php/entwickler.html?show=112

Registry Court/Amtsgericht: Hannover HRB 1712
Managing Directors/Geschäftsführer:
Michael Frankenberg, Werner Sommerfeld, Peter Talke
 
Read Message
Read Message
Previous Topic: Proposal: New optional attibutes on type block
Next Topic: planned passenger capacities
Goto Forum:
  


Current Time: Fri Apr 19 13:47:20 CEST 2024