This spike is to investigate how to handle module name prefixes on CPS-Core outputs

need to consider these questions

1. What are the rules/conventions around using of the module name as prefix in json data
   1. resolve ambiguity, when does it HAVE to be inserted
   2. ODL parsing rules (ODL parser seem to accept/ignore? any prefix)
2. Should we store the (incoming) prefixes in the 'Fragment table
3. Can/should we use ODL SchemaContext object to insert 'missing' prefixes when the paths are not ambiguous?!
4. Extend (PoC) the bookstore model
   1. with unambiguous imports from submodules
   2. with ambiguous imports from submodules