| [railML3] Mandatory <length> element for <track>s [message #2224] |
Thu, 18 July 2019 16:15  |
Christian Rößiger
Messages: 59
Registered: March 2015
|
Member |
|
|
Dear all,
In the current railML schema of version 3.1, one <track> element must
contain 1 or more sub-elements of type <length>. This allows different
lengths (constructional, operational) to be mapped.
From my point of view it is awkward that at least one <length> element
must be specified. For the exchange of timetable data, for example, the
length of a <track> is irrelevant if the infrastructure in the source
and target systems is known.
On the other hand, the scheme only defines that at least one length must
be specified, but not which type (constructional, operational). A system
that can only process one type of length does not benefit from this
constraint.
From my point of view the specification of a <length> for a <track>
element should be completely optional in the next version of the railML
schema. If necessary, the specification of a specific length definition
depending on the usecase can be forced by semantic constraints. What do
you think about this?
Best regards,
Christian Rößiger
--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347
|
|
|
|
Members
Search
Help
Login
Home
