Home » railML newsgroups » railML.infrastructure » ocp's/stations and their properties
Re: ocp's/stations and their properties [message #372 is a reply to message #347] Tue, 02 October 2012 18:11 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Christian,

> And that is the way, how we will do it with railML 2.2.

Very good, thank you.

> However, I still think that concerning the overloading of attributes, we
> should follow the concept that the attributes of a referenced
> "parentOcp" should be overwritten by corresponding attributes from the
> referencing <ocp>.

I agree. The more 'down' it goes in the hierarchy, the more detailed it
is. A parent OCP may have the attribute 'passenger traffic', but that does
not necessarily mean that all children have 'passenger traffic'.

(Example: The parent OCP 'Dresden' has passenger traffic. The child OCP
'Bft. Dresden-Altstadt' does not have. So the children overwrite the
parents.*)

We should make a clear documentation on the priority of overwritten
attributes (parent overwrites child or child overwrites parent). Do you
write it or shall I?

Best regards,
Dirk.

* Many children would wish to have this principle in real life...

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: train relation
Next Topic: Fwd: Mapping of code and abbreviation for ocps
Goto Forum:
  

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

Current Time: Sat May 18 17:09:51 CEST 2024