The mekanika-schema module is one of the few in the mekanika suite that is not coupled directly to the qe related workflow, which renders the specific mekanika prefix unnecessary. The name "schema" itself is a little ambiguous: does it refer to "a" schema, "the" library, the "concept" of schema or something else.. Creating a unique name for the library clears that up.
The
mekanika-schema
module is one of the few in the mekanika suite that is not coupled directly to theqe
related workflow, which renders the specificmekanika
prefix unnecessary. The name "schema" itself is a little ambiguous: does it refer to "a" schema, "the" library, the "concept" of schema or something else.. Creating a unique name for the library clears that up.Propose moving
mekanika-schema
toskematic
: