Adding a +1 for cross-ontology link types as a feature.
We have some large object types (e.g. anything with embeddings) which use a lot of ontology volume. In order to link them to objects in multiple ontologies, we have to duplicate the object in each ontology which is pretty wasteful.
With cross-ontology links we could place objects in a common multi-org ontology and link them to the two respective organization ontologies. I would expect the link to only be visible if the user could see the object type on both sides, and have permission on the link type itself.
Hey - a workaround that I’ve done is to “fake link” the object types. Ie, instead of using search arounds, you can just filter by the primary/foreign.
For example, if object type A has a property that represents the PK of object type B, and you want to perform a search around from object set B to object set A, you can instead just filter object set A on its foreign key property, using the primary keys from object set B.
+1 Support for cross Ontology / account dependency / use.
For example if some company was to build their Ontology as “the” ontological way to interact with their System, it would be great to just build directly on that. Let Foundry manage the integration with their backend system.