Home » railML newsgroups » railml.interlocking » What is the rationale for multiple <assetsForIL>s?
What is the rationale for multiple <assetsForIL>s? [message #2060] Fri, 28 December 2018 23:00 Go to previous message
Thomas Nygreen JBD is currently offline  Thomas Nygreen JBD
Messages: 68
Registered: February 2017
Member
Dear all,

I cannot find any documentation of what should determine which assets that go into which <assetForIL>. I assume that there is a reason why the schema allows multiple <assetsForIL>s, but I cannot find that reason in the drafted tutorial or in the forum.

What is the rationale for multiple <assetsForIL>s? If we look to the infrastructure domain, the closest relative to <assetForIL> is <functionalInfrastructure>, which does not multiply. So why not remove <assetsForILs> and have only one <assetsForIL>?

Best regards,
Thomas Nygreen

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Flank protection
Next Topic: Restricted Areas: limitedBy vs. elements inside
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Apr 28 02:12:34 CEST 2024