Re: missing bitMask at <trainPart><operatingPeriodRef> [message #812 is a reply to message #804] |
Mon, 17 September 2012 16:11 ![Go to previous message Go to previous message](/forum/theme/default/images/up.png) ![Go to next message Go to previous message](/forum/theme/default/images/down.png) |
Joachim Rubröder railML
Messages: 0 Registered: November 2019
|
|
|
|
Dear all,
if you both agree, that the use of operatingPeriods should be restricted
to references, we could implement it this way:
https://trac.assembla.com/railML/ticket/158
Kind regards...
Joachim
--
Joachim Rubröder
Schema Coordinator: railML.timetable
Dirk Bräuer wrote:
>
> Dear all,
>
>> as a general rule, I see absolutely no point in providing alternative
>> means of expressing one and the same thing. It only drives up the cost
>> of implementing the standard.
>> I would therefore pledge for removing these attributes from the
>> trainPart element and strictly restrain the standard to use of
>> operatingPeriods.
>
> It is not so easy with redundancies. Of course we should avoid them as
> much as possible. But sometimes we can hardly avoid them without risking
> that RailML will not be accepted in practice.
>
> In this special case I agree with Andreas; from our side no objection
> against fully deleting (declaring deprecated) everything but the
> <operatingPeriodRef>.ref.
>
> Dirk.
>
>
--
----== posted via PHP Headliner ==----
|
|
|