Forum: railml.common » railML 3.x: Data Modelling Patterns

Home » railML newsgroups » railml.common » railML 3.x: Data Modelling Patterns

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

Re: railML 3.x: Data Modelling Patterns [message #2019 is a reply to message #1915]

Thu, 22 November 2018 11:28

Dirk Bräuer
Messages: 311
Registered: August 2008

Senior Member

Dear Christian and all,

there is already a lot of reply for this topic, so I reduce my words (this time ;-) ) to a short summary concerning two issues which are very important for me:

1) Hierarchy

I think a rather flat hierarchy has no advantage. I prefer a good (possibly deep) hierarchy especially in a very 'technical' context. I already have often the problem of needing to 'jump' very often in the railML files (when reading manually) to resolve references.

Additionally, when I made the suggestion of a possible generic model for future <TT> (with a very flat hierarchy), it was widely refused because of too less structure. So, I am probably (obviously) not the only one with this opinion.

2) Default values

I want to encourage what Christian Rößiger wrote. We cannot avoid default values. It is highly unreasonable for everyone to write "operationalStopOrdered=..." each time when there is no operational stop up to the horizon. Same applies e. g. to "guaranteedPass=..." which does not make sense when there is no pass but a stop. I would simply be more confusion than helping for someone who reads the railML file.

We have plenty of such examples in <TT>.

Best regards,
Dirk.

Report message to a moderator

[Message index]

		railML 3.x: Data Modelling Patterns By: christian.rahmig on Fri, 18 May 2018 09:01
		Re: railML 3.x: Data Modelling Patterns By: christian.rahmig on Fri, 17 August 2018 16:51
		Re: railML 3.x: Data Modelling Patterns By: Christian Rößiger on Wed, 14 November 2018 16:05
		Re: railML 3.x: Data Modelling Patterns By: Joerg von Lingen on Mon, 19 November 2018 05:25
		Re: railML 3.x: Data Modelling Patterns By: Cédric Lavanchy on Mon, 19 November 2018 12:49
		Re: railML 3.x: Data Modelling Patterns By: Thomas Nygreen JBD on Fri, 28 December 2018 22:14
		Re: railML 3.x: Data Modelling Patterns By: Joerg von Lingen on Sat, 29 December 2018 05:08
		Re: railML 3.x: Data Modelling Patterns By: Thomas Nygreen JBD on Thu, 03 January 2019 18:50
		Re: railML 3.x: Data Modelling Patterns By: Thomas Nygreen JBD on Thu, 03 January 2019 21:22
		Re: railML 3.x: Data Modelling Patterns By: Thomas Nygreen JBD on Fri, 11 January 2019 17:09
		Re: railML 3.x: Data Modelling Patterns By: Dirk Bräuer on Thu, 22 November 2018 11:28
		Re: railML 3.x: Data Modelling Patterns By: Joachim.Rubröder on Tue, 27 November 2018 16:08
		Re: railML 3.x: Data Modelling Patterns By: Martin Karlsson on Tue, 11 December 2018 13:48
		Re: railML 3.x: Data Modelling Patterns By: Joerg von Lingen on Wed, 12 December 2018 06:02
		Re: railML 3.x: Data Modelling Patterns By: christian.rahmig on Tue, 18 December 2018 22:17
		Re: railML 3.x: Data Modelling Patterns By: Thomas Nygreen JBD on Fri, 28 December 2018 21:39
		Re: railML 3.x: Data Modelling Patterns By: christian.rahmig on Wed, 16 January 2019 10:26
		Re: railML 3.x: Data Modelling Patterns By: Thomas Nygreen JBD on Mon, 21 January 2019 14:56

Previous Topic:	[railml3.1] Change "v" to "speed" in attribute names
Next Topic:	More standard attributes for objects

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Apr 29 14:08:38 CEST 2024