-
Story
-
Resolution: Unresolved
-
Medium
-
None
-
None
This spike is to investigate how to handle module name prefixes on CPS-Core outputs
need to consider these questions
- What are the rules/conventions around using of the module name as prefix in json data
- resolve ambiguity, when does it HAVE to be inserted
- ODL parsing rules (ODL parser seem to accept/ignore? any prefix)
- Should we store the (incoming) prefixes in the 'Fragment table
- Can/should we use ODL SchemaContext object to insert 'missing' prefixes when the paths are not ambiguous?!
- Extend (PoC) the bookstore model
- with unambiguous imports from submodules
- with ambiguous imports from submodules