| Re: railML 3.x: Data Modelling Patterns [message #2072 is a reply to message #2069] |
Thu, 03 January 2019 21:22   |
Thomas Nygreen JBD
Messages: 68
Registered: February 2017
|
Member |
|
|
Dear all,
One more comment regarding naming of subelements and attributes. In general, I find that most attributes and subelements are named in a self-explanatory way, adhering to the described patterns. But there are a few exceptions, both regarding not repeating element names in attribute names and using verbs in boolean attributes. The repetition rule in Christian's presentation does not apply to elements, but in some cases it should. For instance, the IL element <ownsATPdevice> has a child element <atpDevice> (also a case of inconsistent capitalisation of abbreviations).
Regarding naming of boolean attributes, most without a verb are in IS:
common3.xsd
(Line 685) @negated
infrastructure3.xsd
(Line 1422) @virtual
(Line 1432) @switchable
(Line 1471) @cleaning
(Line 1476) @fueling
(Line 1481) @loadingFacilities
(Line 1486) @maintenance
(Line 1491) @parking
(Line 1496) @preheating
(Line 1501) @ramp
(Line 1506) @toiletDischarge
(Line 1511) @waterRestocking
(Line 1516) @sandRestocking
(Line 1521) @electricSupply
(Line 3113) @regenerativeBrakingAllowed (switch suffix verb to prefix)
(Line 3122) @complianceTSIRequired (switch suffix verb to prefix)
(Line 3192) @powerLimitationRequired (switch suffix verb to prefix)
(Line 3207) @automaticDroppingDeviceRequired (switch suffix verb to prefix)
(Line 3252) @switchOffBreaker
(Line 3257) @lowerPantograph
(Line 3271) @switchOffBreaker
(Line 3276) @lowerPantograph
(Line 3281) @changeSupplySystem
interlocking3.xsd
(Line 178) @autoNormalisation
(Line 622) @automaticKeyRelease
(Line 627) @automaticKeyLock
(Line 1594) <automatic> (NB: boolean element)
Best regards,
Thomas Nygreen
Railway capacity engineer
Jernbanedirektoratet
|
|
|
|
Members
Search
Help
Login
Home
