[x] I have done a quick search on the issue tracker to check if the feature request is not redundant
Is your feature request related to a problem? If yes, describe the problem
Currently commands have to have hard coded references to specific OML vocabulary. It is preferred if these commands can be configured similar to Table, Tree, or Diagram layouts.
Describe the desired feature
Currently OML Vision has the following commands (there may be more) defined which are depend on vocab which is hard coded into the codebase:
refactor these commands so they aren't hard coded into OML Vision, but instead are defined in the OML Git repo. OML Vision API takes care of refactoring those commands to work with OML Vision webviews.
Make OpenAPI/Docusaurus documentation for the OML Vision command API
Make a validator or regression test for the OML Vision command API
Additional context
Given OML Vision commands which depend on hard coded OML vocab, then create API in OML Vision which allows users to create their own commands
Given OML Vision commands API, then create OpenAPI/Docusaurus documentation for the OML Vision commands API
Given OML Vision commands that don't depend on hard coded OML vocab, then create validator for commands (can probably use CUE)
Checklist before submitting a feature request
Is your feature request related to a problem? If yes, describe the problem
Currently commands have to have hard coded references to specific OML vocabulary. It is preferred if these commands can be configured similar to Table, Tree, or Diagram layouts.
Describe the desired feature
Currently OML Vision has the following commands (there may be more) defined which are depend on vocab which is hard coded into the codebase:
CREATE_FCR EXECUTE_DELETE_ELEMENTS GET_ELEMENT_DEPENDENCIES UPDATE_CM_STATE
The scope of this ticket is to
Additional context