Home » railML newsgroups » railml.timetable » <trackRef>.dir
Re: <trackRef>.dir [message #798 is a reply to message #795] Wed, 30 May 2012 16:17 Go to previous message
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
Hi Dirk,

Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
> Am 29.05.2012, 13:45 Uhr, schrieb Susanne Wunsch <coord(at)commonrailmlorg>:
>
>> Currently the absence of the attribute has the same semantics as the
>> attribute "dir" with value "unknown". I don't know if these two
>> possibilities of defining the same meaning introduce any troubles in
>> programming.
>
> From my experience: No problem, full redundancy. From my side we
> should avoid 'unknown' and leave the possibility to skip the
> attribute.

Ok, I will define a new type for only these two enumeration
values. Something like "tStrictDirection" for "up" and "down" without
any extensibility options.

>> We keep in mind that there will be a renaming of the enumeration values
>> in next major release (raising, falling).
>
> Can we exchange "keep in mind" with "create a track ticket"? ;-)

Already done. [1]

> Or expand the track ticket you already created for the same renamings
> in IS ?

Joachim appended a comment for not forgetting this topic. :)

[1] http://trac.assembla.com/railML/ticket/145

Nice development speed. :))

Gratefully ...
Susanne

--
Susanne Wunsch
Schema Coordinator: railML.common
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: RFE for stop description
Next Topic: missing bitMask at <trainPart><operatingPeriodRef>
Goto Forum:
  


Current Time: Thu May 16 20:08:55 CEST 2024