Skip to content
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

Fixes xml:base and default namespace declarations #9

Merged
merged 1 commit into from
Dec 12, 2018
Merged

Fixes xml:base and default namespace declarations #9

merged 1 commit into from
Dec 12, 2018

Conversation

hlapp
Copy link
Contributor

@hlapp hlapp commented Dec 12, 2018

The fact that these have presumably been left at initial (Protégé-suggested?) default settings happens to be inconsequential in the current version of the document, because all IRIs are given as absolute ones, and all XML elements use an explicit namespace, including the ones from this ontology.

That said, arguably they should be set to meaningful values, so that if in the future an ontology editor were to use a relative URI or a term from this ontology without namespace, then the presumably "correct thing" would happen. For example, setting the default namespace (xmlns) correctly means you can write

<NOMEN_0000001>1960</NOMEN_0000001>

instead of

<obo:NOMEN_0000001>1960</obo:NOMEN_0000001>

and they would both result in the exact same axiom.

The other advantage is this change would eliminate a source of confusion as to what the namespace of this ontology is, see for example pensoft/OpenBiodiv#44.

The fact that these have presumably been left at initial (Protégé-suggested?) default settings happens to be inconsequential in the current version of the document, because all IRIs are given as absolute ones, and all XML elements use an explicit namespace, including the ones from this ontology.

That said, arguably they should be set to meaningful values, so that if in the future an ontology editor were to use a relative URI or a term from this ontology without namespace, then the presumably "correct  thing" would happen. For example, setting the default namespace (`xmlns`) correctly means you can write
```xml
<NOMEN_0000001>1960</NOMEN_0000001>
```
instead of
```
<obo:NOMEN_0000001>1960</obo:NOMEN_0000001>
```
and they would both result in the exact same axiom.

The other advantage is this change would eliminate a source of confusion as to what the namespace of this ontology is, see for example pensoft/OpenBiodiv#44.
@mjy mjy merged commit 107d29f into SpeciesFileGroup:master Dec 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants