| Re: railML 3.x: Data Modelling Patterns [message #2026 is a reply to message #1915] |
Tue, 27 November 2018 16:08   |
Joachim.Rubröder
Messages: 33
Registered: September 2004
|
Member |
|
|
Dear all,
I generally agree with the design patterns, as long as we really try to respect them within all railML 3.x domains in order to create a common look and feel for railML.
1) "Hierarchy:" Ok, Container/Object/Parts (or Components) would correspond with trains/train/trainParts. Views could be "commercial trains", "operational trains", "ordered slots", ...
2) "Naming": Ok, so there will be lots of boolean attributes like "isThis" or "hasThat"
3) "Boolean information": Option 1, a dedicated "unknown" should be part of an enumeration together with "assumed", "irrelevant", ...
4) "References": Option 1, because the linking might not be as straight forward as intended. A train could belong to several different kind of train categories.
Best regards,
Joachim
--
SMA und Partner AG
Gubelstrasse 28, CH-8050 Zürich
www.sma-partner.com
|
|
|
|
Members
Search
Help
Login
Home
