Current MarSystem/Control paths are something like:
IMHO this style is confusing because it looks like a path down a hierarchy, as we are used to with the file systems on our computers , but with a strange twist: each steps down the hierarchy corresponds with two components in the "path": a type and a name: "type/name/type/name/type/name".
Wouldn't it improve readability to change the separator between the type and name with a colon ("type:name")? For example:
This colon-form could be supported together with the traditional all-slash-form, which could become deprecated but still allowed to make sure old code stull works.
I never understood the need to specify the type in a MarSystem/Control path, as it is redundant. Is it for clarity? Is it to be able to do a consistency check?
Anyway, why not just use the following?
Of course, this would breaks compatibility, unless a different separator would be introduced, like ">":