Is there an existing issue for this?
Current Behavior
Even though we have customized the Default Base URI Domain in Ontobricks, the URI of an individual domain still reverts to https://databricks-ontology.com intermittently when generating e.g. R2RML.
This has been observed primarily after loading another domain, restarting the server or similar.
The result can be loading wrong URI's into the knowledge graph.
Expected Behavior
After specifying the Base URI for a domain the resulting URI's are persisted across both ontologies and mappings, and not regenerated based on the global configuration.
Regardless of whether the Base URI of the domain is custom or auto-generated, it should be persisted as the source of truth and only updated in OWL and R2RML if changed at the domain level later.
Steps To Reproduce
- Assign a global default base URI
- Create a domain using the default.
- Create ontology, mappings.
- Restart the server or similar
- Go straight to R2RML mappings and observe the URI has reversed to the
https://databricks-ontology.com default.
Cloud
Azure
Browser
Edge
OntoBricks Version
0.5.1
Relevant log output
Additional Context
No response
Is there an existing issue for this?
Current Behavior
Even though we have customized the Default Base URI Domain in Ontobricks, the URI of an individual domain still reverts to
https://databricks-ontology.comintermittently when generating e.g. R2RML.This has been observed primarily after loading another domain, restarting the server or similar.
The result can be loading wrong URI's into the knowledge graph.
Expected Behavior
After specifying the Base URI for a domain the resulting URI's are persisted across both ontologies and mappings, and not regenerated based on the global configuration.
Regardless of whether the Base URI of the domain is custom or auto-generated, it should be persisted as the source of truth and only updated in OWL and R2RML if changed at the domain level later.
Steps To Reproduce
https://databricks-ontology.comdefault.Cloud
Azure
Browser
Edge
OntoBricks Version
0.5.1
Relevant log output
Additional Context
No response