Unregistered OBO namespaces appear in ontobee #15
Comments
|
This will be a big change. I don't know how many ontologies will be affected. We will probably need to do a survey first. For those that will be affected, do we have any recommendation for them? Anyway, they want to follow OBO foundry principles and become part of the initiative. If we reject them, I don't know if it is a big hit to their project. It may also hurt the OBO because these ontologies were generated before a formal policy is set up. Also, we probably need a more formal policy on this with a written document and agreement by the foundry. Oliver From: Alan Ruttenberg [notifications@github.com] The only ontologies sanctioned to use the namespace http;//purl.obolibrary.org/obo/xxx are those where xxx are listed in an id tag ontobee should generate a 404 for any request that is not using a registered namespace. This is triggered by working on https://code.google.com/p/obo-foundry-operations-committee/issues/detail?id=137 and noticing that they use ids like ARG_xxxxxx However I notice that ICO is also doing that. It should also not appear on ontobee until the namespace is registered. — Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues |
|
It's fine to do a survey, but the architecture of the web make clear that the domain name owner has authority on the URIs in its domain. Also, the OBO namespace policy and id policy are well documented and have been in place for a good amount of time. So perhaps rather than having a survey it would be better to give notice and assist with either having namespaces registered or changing URI to not use the the domain purl.obolibrary.org if groups don't want to do that. As I mentioned, plans are underway, in any case, to address this issue upstream but there are some technical issues that need to be resolved. It is considered a bug that unregistered purls are redirected. In any case, I'd rather that we're all on the same page about solving the problem. A first step might be to have a banner on pages with unauthorized namespaces explaining the issue, suggesting that users contact the ontology developer to have them register the namespace and explaining that unregistered purls will cease to work at some point. Note this only applies to urls that are below http://purl.obolibrary.org/ |
|
Oliver, we do have written documents on this policy. http://obofoundry.org/id-policy.shtml is the OBO foundry policy on registration and http://en.wikipedia.org/wiki/Domain_name among other resources describe how domain names work. Regards, |
|
There seems a problem with the website: Oliver From: Alan Ruttenberg [notifications@github.com] Oliver, we do have written documents on this policy. http://obofoundry.org/obo/id-policy.shtml is the OBO foundry policy on registration and http://en.wikipedia.org/wiki/Domain_name Regards, — Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues |
|
I tried to fix the post. http://obofoundry.org/id-policy.shtml On Tue, Jun 10, 2014 at 3:44 PM, ontoden notifications@github.com wrote:
|
The only ontologies sanctioned to use the namespace
http;//purl.obolibrary.org/obo/xxx
are those where xxx are listed in an id tag
https://code.google.com/p/obo-registry/source/browse/trunk/metadata/ontologies.txt
ontobee should generate a 404 for any request that is not using a registered namespace.
Later we will likely put in technical mechanisms that prevent these from being redirected in the first place.
This is triggered by working on https://code.google.com/p/obo-foundry-operations-committee/issues/detail?id=137 and noticing that they use ids like ARG_xxxxxx
However I notice that ICO is also doing that. It should also not appear on ontobee until the namespace is registered.
The text was updated successfully, but these errors were encountered: