Home » railML newsgroups » railml.common » Consolidated Use Cases List (Should the UCs be presented in one consolidated list or per subschema)
Consolidated Use Cases List [message #1958] Mon, 10 September 2018 15:10 Go to previous message
Ferri Leberl is currently offline  Ferri Leberl
Messages: 24
Registered: September 2016
Junior Member
Dear All,

There has been a discussion whether to consolidate the UC lists or whether to stick to the current solution with separate UC lists per subschema.
As a demonstration, I have made up a consolidated list which can be found under
https://wiki.railml.org/index.php?title=UC:Use_cases/table
Currently, both this list and the lists by subschema are linked under
https://wiki.railml.org/index.php?title=UC:Use_cases#Lists_o f_Use_Cases_per_subschema

The coordinator would prefer to go on with the consolidated list as it is more efficient to maintain and offers a broader view. However, the consolidated list is more difficult to overlook.
We want to avoid offering both the consolidated list and the existing ones for maintenance reasons.

Can we declare it a consent to skip the old lists and keep the consolidated one?

Thank you for your responses.
Ferri Leberl

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: @minOccurs, @maxOccurs and @use
Next Topic: Define requirements for processContent strictly than lax
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Apr 25 21:54:34 CEST 2024