Home » railML newsgroups » railml.common » [railML3] status and life cycle (Common) (Approaching a generic modelling of states and life cycle stages)
[railML3] status and life cycle (Common) [message #2850] Mon, 22 November 2021 12:29 Go to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 392
Registered: January 2016
Senior Member
Dear railML community,

in recent discussions in various use case working groups we discovered a common need for modelling life cycle aspects and stages.

We started this development in the infrastructure domain: Within domain <infrastructure> you can find a view named <infrastructureStates> where all information about infrastructure states are modelled. It is possible to model the state of a whole infrastructure as well as the state of single infrastructure components. Possible values for <infrastructureState>@value are: closed, conceptual, disabled, operational, planned

The interesting question: Who / which use case needs modelling of life cycle states and what are its specific requirements? We want to use this forum thread to collect the various requirements and ideas. In the then following conclusion, we want to find out, how "generic" the topic can be solved in the Common part or whether we should implement states independently in the domains where they are needed (infrastructure, timetable? ...)

So, dear all, what do you need for modelling different states? As always, any feedback is highly appreciated.

Best regards
Christian


Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [railML3] status and life cycle (Common) [message #2860 is a reply to message #2850] Thu, 09 December 2021 16:21 Go to previous messageGo to next message
Milan Wölke is currently offline  Milan Wölke
Messages: 120
Registered: April 2007
Senior Member
Hi Christian,

is this perhaps related to the question of how to commonly handle validities, i.e. when sth is operational/happens and when it is not? If so, we for sure have an overlap there as this is what timetable is all about. Regarding states like the ones you mentioned, I will bring this up in out next phone conference in January.

Best regards, Milan


Milan Wölke - Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [railML3] status and life cycle (Common) [message #2884 is a reply to message #2860] Thu, 20 January 2022 11:53 Go to previous message
Thomas Langkamm is currently offline  Thomas Langkamm
Messages: 22
Registered: April 2019
Junior Member
This topic is IMHO very much related to this thread here: https://www.railml.org/forum/index.php?t=msg&th=834& start=0&
Maybe we should discuss both in one thread and close the other?
Previous Topic: Possession Mgmt Use-Case
Next Topic: [railML3] Refactoring of OrganizationalUnits
Goto Forum:
  


Current Time: Sun May 29 04:03:09 CEST 2022