Forum: railML.infrastructure » [railML3] Restricting aggregation of RailTopoModel

Home » railML newsgroups » railML.infrastructure » [railML3] Restricting aggregation of RailTopoModel (New semantic constraints suggested)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: [railML3] Restricting aggregation of RailTopoModel [message #3258 is a reply to message #3237]

Fri, 21 June 2024 13:20

christian.rahmig
Messages: 447
Registered: January 2016

Senior Member

Dear railML community,

as there have been no reactions so far, I assume that you all agree with the proposed semantic constraints on aggregation of topology.
If that conclusion is not correct, please let us know your feedback and ideas, so that we can incorporate them in the development of upcoming railML 3.3.

Thank you very much and best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]

		[railML3] Restricting aggregation of RailTopoModel By: Larissa Zhuchyi on Mon, 29 April 2024 17:13
		Re: [railML3] Restricting aggregation of RailTopoModel By: christian.rahmig on Fri, 21 June 2024 13:20

Previous Topic:	Balise group values for IS:functionalType
Next Topic:	[railML3] Type of a name of an operational point

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Jul 22 12:22:08 CEST 2024