-
Notifications
You must be signed in to change notification settings - Fork 18
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
Remove default prefix #898
Comments
Agreed. @dylan-sa and I observed this somewhere and wondered if Protege was adding it. If so, we could include removing it in the pre-commit hook that deletes the skos annotation declarations. |
We would need a process that runs after the serializer to remove the base declaration. Could include in the serializer pre-commit. DECISION: Include in the serializer pre-commit and the release process. |
@sa-bpelakh Please confirm that this is indeed inserted by the serializer before you begin this implementation. Possibly I'm misremembering. |
@uscholdm Do we want to ask the EDM Council to add this as an option to the serializer? |
It worked before, so it might work again - especially since use of Protege is so widespread. We'd need to have a clear example to hand them. A ton of experiments were done, that would have to be condensed, clear and concise. |
I checked, and the serializer does not re-add the default namespace if it is removed manually. If I modify the commit hook to remove it anyhow, and then push in a single commit removing it from every ontology, we won't even need to have it as a step in the build - unless you think someone out there is bypassing the commit hook. |
That could happen if a setup is not done correctly or gets corrupted. |
DECISION: The pre-commit hook should remove the default prefix (similarly to how it removed stub SKOS definitions previously). There is a new issue, #1094, to remove it manually for the 13.0.0 release. |
I seem to remember seeing something that recommended that ontology files should not have default prefix statements (the blank or
:
namespace). I don't know why we'd want to use one in gist but I see one in gistCore. I suggest we remove it.The text was updated successfully, but these errors were encountered: