databrickslabs / databrickslabs/ontobricks
[FEATURE]: select relationships/entities from pre-existing/imported ontologies instead of redefining them
@benoitcayladbx is already working on this.
Since Jul 29, 2026.
- Dominant language
- Python
- Stars
- 377
- Forks
- 69
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 5
Description
Is there an existing issue for this?
- I have searched the existing issues
Problem Statement
Today, adding a relationship or entity in the Business Views designer means defining a new property or class from scratch, even when a semantically identical, widely used relationship or entity already exists in a standard vocabulary (e.g. dcterms, prov, skos, xsd, ...).
There's currently no way to search across relationships and entities already defined in the domain/registry, or available from an imported ontology, and select one directly.
This matters beyond convenience: models built with standard, widely recognised relationships and entities are far easier to align, merge, or federate with other ontologies. It promotes interoperability, trust and effort.
Proposed Solution
When creating a property/edge in the designer, offer a search/picker over:
- properties already defined elsewhere in the same domain or registry, and
- ship a small set of foundational vocabularies (SKOS, Dublin Core, PROV-O, XSD) available for import/reuse out of the box, since these are extremely commonly reused relationship vocabularies in RDF/OWL modeling generally, distinct from the domain-specific industry ontologies already supported.
Area
Ontology Management
Additional Context
This ties into the earlier issue [#42 ] about integrating ontologies, but from a different angle.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.