Thank you a lot for the insight. One thing that comes to my mind is that I have to reload the ontology manager each time I published a new function e.g. backing an action type. When loading the data on demand it would be nice to always get the latest version info when choosing from the respective dropdowns. This would greatly improve the workflow. I actually did not think that the data was not loaded upfront since I always had to reload if there was new info.
Another thing that would be awesome: Check action permissions with example settings / objects for other users. When having complex validation logic it would be great to test this by putting the hat on of another user end trying to execute the action e.g. in a scenario environment.
For the interoperability with other ontologies e.g. OWL-based that are external to Foundry, it would be great to have more export-options or query endpoints. While it is appreciated that one can get the “complete” ontology metadata via a single get endpoint, it lacks a lot of information. While the type classes are only a sidenote compared to how the ontology manager worked a few years ago, they could be an extremely useful way of assigning object types and relations e.g. to OWL concepts for integrating Foundry with other knowledge management systems.
Furthermore, there are several things that are not "complete” when it comes to the OWL syntax. Link types do not have an “inverseOf” property - pointing to the exact inverse of a relationship. This can be useful for object traversal back and forth, if there are multiple link types between to object types (or one object type itself).
Having some experience with open source ontology frameworks, I do appreciate the easiness of use in the ontology manager and also the possibility for having pullrequests to seamlessly evlove the ontology. You do not have to understand triple syntax or how SPARQL works as it is required when looking at ontology languages like “foaf” or “OWL”. More compatibility with those frameworks would be really nice, though ![]()
There are several threads regarding those topics in this forum and I am looking forward to having more discussions - how to integrate the ontology in a highly diversified enterprise landscape.
Best,
Florian