Replies: 9 comments 3 replies
-
owl-adapter#58 Support OML ontologies importing OWL ontologies directly (i.e., without first converting the OWL to OML). |
Beta Was this translation helpful? Give feedback.
-
Support OML text files (*.oml) importing OML XMI (oml.xmi) and OML JSON (.omljson) files. |
Beta Was this translation helpful? Give feedback.
-
Support a CoPilot (AI Assistant) feature for OML editors as part of the next-gen OML Vision IDE (VS Code extension). |
Beta Was this translation helpful? Give feedback.
-
Support simpler import resolution mechanism than XML catalogs, by declaring ontology paths that may be folders or jar files. |
Beta Was this translation helpful? Give feedback.
-
Support a .oml.yml file that declares the main settings of an OML project and which can be read by the build script. |
Beta Was this translation helpful? Give feedback.
-
Support an OML CLI that helps create new OML projects and perform common editing/analysis tasks from a terminal. |
Beta Was this translation helpful? Give feedback.
-
Improve default ontology diagrams in OML Luxor to be on par or better with those in OML Rosetta |
Beta Was this translation helpful? Give feedback.
-
Add the ability to define multiple OML ontologies in the same model file |
Beta Was this translation helpful? Give feedback.
-
Add support for Punning (using the same name to denote a class and an individual) to OML |
Beta Was this translation helpful? Give feedback.
-
Hey all. I would like to start planning the scope of the next major revision (v3.0) of OML and its tooling ecosystem and I like to get input from you all. So if you like to propose a new feature or an enhancement, please add a comment to this discussion item (optionally referencing a Github issue describing your request further). You can also "upvote" a feature and enhancement proposed by others. This will be a good way for the maintaining team to prioritize the scope of OML 3.0.
Beta Was this translation helpful? Give feedback.
All reactions