Forum: railML.infrastructure » [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation

Home » railML newsgroups » railML.infrastructure » [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation (Ensuring that each netElement and netRelation belongs to exactly one RTM:level)

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

Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation [message #3995 is a reply to message #3590]

Wed, 06 May 2026 17:52

Milan Wölke
Messages: 231
Registered: April 2007

Senior Member

Hi all,

in general I would agree with Larissas Semantic Contraint proposals. They reflect the way I would understand the model. Like David pointed out, connections between netElements of different levels would somehow connect the graphs when this should rather be done using aggregation.

@Mathias: Can you provide some short example how that would look like? I think I am missing something with your scenario. If the netElement is shared between meso and micro, how can you aggregate?

Best regards, Milan

Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]

		[railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Larissa Zhuchyi on Thu, 27 February 2025 16:14
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Rémi Collet on Mon, 03 March 2025 09:05
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: christian.rahmig on Mon, 03 March 2025 13:38
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: David Lichti on Tue, 04 March 2025 11:31
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: christian.rahmig on Mon, 14 April 2025 13:38
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Fredrik Jönsson on Tue, 22 April 2025 13:03
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Stéphane Kaloustian on Tue, 22 April 2025 14:57
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Mathias Vanden Auweele on Wed, 23 April 2025 22:25
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Milan Wölke on Wed, 06 May 2026 17:52
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Mathias Vanden Auweele on Thu, 07 May 2026 20:20
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Larissa Zhuchyi on Thu, 18 June 2026 13:36
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Mathias Vanden Auweele on Thu, 18 June 2026 17:49
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Larissa Zhuchyi on Mon, 07 September 2026 10:00
		Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation By: Larissa Zhuchyi on Mon, 07 September 2026 14:50

Previous Topic:	[railML3] Order of geometricCoordinate attributes
Next Topic:	[railML3.4 beta4] Changed placement of sub-element elementState

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Sep 15 10:32:19 CEST 2026