Home » railML newsgroups » railML.infrastructure » [railML3|alpha] Missing track conditions
Re: [railML3|alpha] Missing track conditions [message #1441 is a reply to message #1440] Tue, 08 November 2016 15:19 Go to previous message
Martin Karlsson is currently offline  Martin Karlsson
Messages: 14
Registered: October 2016
Junior Member
Thanks for your reply. I will consider to enter a use case when time permits. Just a couple of short comments for now:

About electrification, I think after reading your comment that it is best left as it is. It is fully flexible also outside the ERA list. When it does match a list entry, it can easily be translated.

I agree that data should not be modelled twice. In my opinion, data should be decoupled from the function(s) using it, i.e. there should ideally be no ETCS specific objects. A non stopping area is an operational restriction of interest, regardless if it is realised through an ETCS message, a sign post or a written instruction to the driver.


-------------------------
Martin Karlsson
Bombardier Transportation
Rail Control Solutions
EAPD/ECC
S-405 02 Göteborg, Sweden
Visiting address: Polhemsplatsen 5
Tel.: +46 70 6667615
martinkarlsson(at)railbombardiercom
 
Read Message
Read Message
Read Message
Previous Topic: [railML3|alpha] Modelling of track conditions
Next Topic: railML 2.3 infrastructure extension for capacity planning and network statement usecases
Goto Forum:
  


Current Time: Mon May 06 09:34:05 CEST 2024