Home » railML newsgroups » railml.misc » Child elements with one value vs. attributes
Child elements with one value vs. attributes [message #1760] Thu, 12 April 2018 05:39
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 67
Registered: May 2011
Member
Dear all,

in the existing railML schema we have placed the information mainly into attributes. In the current development of IL
part it appears that there are several child elements containing only one value but no attribute at all (variant 1). I
would suggest to transfer such values into an attribute of the parent element whenever this is suitable (variant 2).

1) variant
<rail3:overlapReleaseTimer code="ovt01" id="ovt01">
<rail3:timer>PT60S</rail3:timer>
<rail3:overlapReleaseCondition>startTimerAfterVacating</rail3:overlapReleaseCondition >
</rail3:overlapReleaseTimer>

2) variant
<rail3:overlapReleaseTimer code="ovt01" id="ovt01" timer="PT60S" overlapReleaseCondition="startTimerAfterVacating">
</rail3:overlapReleaseTimer>

Best Jörg.
Interlocking coordinator
Previous Topic: More concise usage of namespaces
Next Topic: railML 3.x: Data Modelling Patterns
Goto Forum:
  


Current Time: Mon May 28 05:05:21 CEST 2018