| Some open topics from a timetabling prospective [message #270] |
Tue, 15 November 2011 13:18 |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hello,
some times ago, Dirk posted some ideas to the timetable forum. I just
now discovered some open topics regarding the infrastructure branch
within all the other useful (already implemented) comments.
"Dirk Braeuer" <dirkbraeuer(at)irfpde> writes:
> The element “mileageChange” includes the attributes "absPosIn" and
> "type". Both of them are now defined as "use=required". This should be
> changed to "use=optional".
>
> It should be possible to define a mileageChange at the very beginning
> of a line as an initial mileage change or descriptor. Such an initial
> mileage change has no "absPosIn" and needs no "type" (or the type is
> something like “initial”).
The mileage start may be defined in 'trackBegin' element. The
'mileageChange' element is meant for changes in the real world along the
track.
> In opposition to this, the attribute "dir" has to be given at every
> line. There is no situation known which makes it impossible to fill
> this attribute. So the use should be changed from "optional" to
> "required".
+1
Are there any objectives against this statement? Christian, do you file
the ticket?
> The element OperationControlPoint includes the attribute
> "abbreviation" which misses an "i".
That's an already known issue. See Ticket #61. [1]
Please use the new attribute 'code' instead of the misspelled.
> An additional element is defined as "Line" which includes the following
> attributes:
> <xs:attribute name="uicNumber" type="xs:positiveInteger"
> use="optional"/>
> <xs:attribute name="lineNumber" type="xs:string" use="optional"/>
>
> It should be possible to define these data independently of the
> attributes "name" or "description".
I would recommend to use the "new attribute" 'code' instead of the
'lineNumber'. It stands for an line-related well-known code.
The 'uicNumber' attribute looks like the UIC country code. That could be
defined for ocps at the element 'ocp/tsi/country'.
Would that help out? Or should we enable the 'tsi' element for 'line'?
Oops, there is currently no wiki page for 'tsi'.
See Trac ticket for more information about it. [2]
Or have a look at the discussion in this forum. [3]
> Some other hints:
>
> The zip-code of an ocp should be defined as a string. For example in
> Great Britain it is not possible to use a numeric-only data
> type. Also, the use should be changed to optional.
I filed a ticket for it. [4]
> The propService may also include the information of an airport
> connection (consequently, since ship and bus are provided).
I filed a ticket for it. [5]
See also a ticket for restructuring current ocp/prop* elements. [6]
I hope it helps. Kind regards...
Susanne
[1] http://trac.assembla.com/railML/ticket/61
[2] http://trac.assembla.com/railML/ticket/112
[3] http://www.railml.org/forum/ro/?group=1&id=64
[4] http://trac.assembla.com/railML/ticket/127
[5] http://trac.assembla.com/railML/ticket/128
[6] http://trac.assembla.com/railML/ticket/63
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
