-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple database acting as source of entities #7
Comments
After discussing this shortly with @francescalb an idea came up to introduce a "personal" or "project-specific" part of the namespace. The main issue here is mapping the URI/URL to different backends/databases/entity storages. So if the difference is introduced in this "core" part of the URL between the current namespace and the version, then that would effectively "fix" this issue, allowing for us to have multiple backends mapping to specific URI/URLs as well as still do all of this through the same service running at My suggestion is to define the URIs as follows:
General namespace: Must be the root URL of the entities service - in the case of onto-ns it is: |
is a good naming scheme for new entities. But I don't think we want to change the names of the build-in or existing entities. |
For requirements on how the URIs should be written, see SINTEF/dlite#788. |
Note, this is true only for the DLite-flavoring. |
Define the modifications of the service to handle multiple databases where entities are stored.
The assumption is that different communities might use different databases to store their entities.
Onto-ns service could then explore and recover these entities and check if the uri exist in one or more of the database, if not return an error, if multiple but exactly equivalent return the entity (but inform the database managers about duplication) and if multiple different return error and inform databases managers.
The text was updated successfully, but these errors were encountered: