| Re: ocp's/stations and their properties [message #378 is a reply to message #372] |
Wed, 03 October 2012 09:25  |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Hello Dirk,
>> 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.*)
thank you for your example, which I am going to include in the wiki
notes. For the sake of completeness I want to add, that the principle of
overwriting requires a corresponding attribute in the child element. In
particular, if the child ocp does not specify the 'passenger traffic'
attribute, the value from the parent ocp is taken.
Your example in source code:
<rail:operationControlPoints>
<rail:ocp id="ocp01" name="Dresden" ...>
<rail:propService passenger="true" />
</rail:ocp>
<rail:ocp id="ocp02" name="Bft. Dresden-Altstadt" ...
parentOcpRef="ocp01">
<rail:propService passenger="false" />
</rail:ocp>
</rail:operationControlPoints>
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
