Forum: railml.timetable » [railML 3] New semantic constraint for trainVariant

Home » railML newsgroups » railml.timetable » [railML 3] New semantic constraint for trainVariant

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

Re: [railML 3] New semantic constraint for trainVariant [message #3061 is a reply to message #3057]

Wed, 15 March 2023 13:39

David Lichti
Messages: 13
Registered: December 2020

Junior Member

This may be a more general topic: But how is the interaction of semantic constraints with custom extensions?

For example, if there was an extension adding a flag for propsed trains, f.ex. <ext:isProposed>. That train would be neither cancelled (because it hasn't been published), nor on-request (because it hasn't been agreed). In such a case it would be reasonable to have more than one proposed variant for one day.

Report message to a moderator

[Message index]

		[railML 3] New semantic constraint for trainVariant By: Milan Wölke on Mon, 13 March 2023 17:22
		Re: [railML 3] New semantic constraint for trainVariant By: David Lichti on Wed, 15 March 2023 13:39
		Re: [railML 3] New semantic constraint for trainVariant By: Milan Wölke on Wed, 05 April 2023 12:25
		Re: [railML 3] New semantic constraint for trainVariant By: Milan Wölke on Tue, 02 May 2023 17:57

Previous Topic:	Semantic Constraints for Train Section
Next Topic:	Extension of railML's Advanced Example

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu May 02 15:27:13 CEST 2024