| Re: Infrastructure element datamodel quality and input-data source [message #3259 is a reply to message #3234] |
Fri, 21 June 2024 13:49   |
christian.rahmig
Messages: 465
Registered: January 2016
|
Senior Member |
|
|
Dear Torben,
thank you for your data model quality input and for your patience waiting for my answer...
Regarding question 2:
From my perspective, elementState can refer to a genericArea, as well as to a projectArea. The question is what is more useful? A genericArea carries relatively little information whereas a projectArea is linked with relevant project meta data. So, I would prefer the projectArea...
Regarding question 3:
I would be very happy and appreciate if you can initiate a data model quality use case and prepare it until the autumn conference. I am sure that the quality topic is interesting also for other members of the community...
Regarding question 1:
Well, this is of course closely linked with question 3. So, before we introduce a string attribute somewhere for information that could be structured in more detail, I prefer to go for the full solution with railML 3.4. But if you and the community have an urgent need, let's find a straight and low-level work-around...
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
