Home » railML newsgroups » railML.infrastructure » Haltetafel / stop post
Re: Haltetafel / stop post [message #393 is a reply to message #392] Fri, 19 October 2012 15:58 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Christian,

thank you for implementing the extended attributes.

> However, I would skip these detailed view and leave it open to the user
> if he/she refers to a minimum or maximum value.

I think this is a solution which should not be intended by RailML. In the
last developing steps of RailML, we tried hard to clarify existing
possible misunderstandings. Here, we create a new one.

Please be aware that normally there are at least _two_ "users" of the
RailML scheme: The writing and the reading software. How should the
writing software tell to the reading software whether "he/she refers to a
minimum or maximum value"? It was agreed in RailML that any clarification
by scheme is better than one by Wiki.

So, please help the writing software to clarify whether "he/she refers to
a minimum or maximum value" by creating the min/max... attributes.

Regards,
Dirk.

P.S.: To answer your tramway example: If the writing software does want to
avoid the 30 m train using the 45 m stop post: It can place a
"minTrainLength=31 m" and "maxTrainLength=45 m" attribute at the 45 m stop
post, so the 30 m train has only one choice.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Shown values on mileposts
Next Topic: Steckenunterbruch/line blocking
Goto Forum:
  


Current Time: Wed May 08 20:39:45 CEST 2024