| Re: Haltetafel / stop post [message #461 is a reply to message #434] |
Thu, 22 November 2012 10:55   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear Susanne and other railML users,
>> in order to be able to handle all three types of stop post validity, I
>> suggest to define three boolean parameters "min", "max" and
>> "interpolating".
>
> Do you want to allow multiple value to be used for one stop post?
>
> If only one constraint should be allowed (min, max, interpolating _or_
> unknown) than there should be an attribute with an extensible
> enumeration list be provided.
I agree.
>> The advantage of the boolean parameters is that they can be combined
>> with the axleCount as well as with the trainLength and the
>> wagonCount. Alternatively, the definition of a minimum, a maximum and
>> an interpolating parameter for each of the attributes is required and
>> thus, does not allow for unspecified stop posts.
>
> I'm sorry, I don't understand _this advantage_. I would asume that one
> attribute with an enumeration list would help out in a similar way.
Of course, you are right. The advantage I meant referred to the direct
combination of the constraint with the attribute in one word, e.g.
"minAxleCount" or "maxAxleCount".
> <stopPost id="sp1" axleCount="40" ruled="max" .../>
> <stopPost id="sp2" axleCount="80" ruled="max" .../>
> <stopPost id="sp3" trainLength="100" ruled="interpolating" .../>
> <stopPost id="sp4" trainLength="200" ruled="interpolating" ../>
>
> I would prefer a better name for this attribute: "ruled",
> "constraint"...
How about an enumeration parameter named "bounding"?
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
