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

non-OBO PURLs in Foundry ontologies #2667

Open
wdduncan opened this issue Dec 21, 2024 · 5 comments
Open

non-OBO PURLs in Foundry ontologies #2667

wdduncan opened this issue Dec 21, 2024 · 5 comments
Labels
attn: OFOC call Issue to discuss on fortnightly OBO Operations meeting ontology metadata Issues related to ontology metadata

Comments

@wdduncan
Copy link
Member

wdduncan commented Dec 21, 2024

Making an issue for question asked on the google group.

I am working with a group that wants to use the Behavior Change and Intervention Ontology (BCIO) in conjunction with OBO ontologies (e.g., mental functioning ontology).

If they want to submit their ontology to the OBO Foundry, do we allow these ontologies to use non-OBO PURLs? For example, BCIO has the relation 'has study sample':
http://humanbehaviourchange.org/ontology/BCIOR_000001

Although BCIO is the specific use case, there are ontologies to consider (e.g., the Common Core Ontologies or Industrial Ontologies Foundry).

Possible principles for using non-OBO purls:

  • The IRI must resolve in a web browser
  • PURLs not to use their own domain name
  • Some kind of good-faith but strong evidence that a bespoke URL base will continue to be maintained after funding ends

I'm on the fence about this. On one hand, I like it b/c it avoids OBO ontologies duplicating work done elsewhere. But, on the other hand, it may introduce a lot of crap into the OBO Foundry space.

Perhaps we classify ontologies using non-OBO PURLs as so-called "application ontologies". I'm also in favor of permitting application ontologies to inject axioms (see discussion here).

cc @cmungall @matentzn @addiehl

@nlharris nlharris added the ontology metadata Issues related to ontology metadata label Dec 22, 2024
@cmungall
Copy link
Contributor

cmungall commented Dec 23, 2024 via email

@wdduncan
Copy link
Member Author

I would strongly recommend that groups do not use their own domain name
in PURLs
Interestingly, the BCIO is part of a larger effort: The Behavioural and Social Sciences Ontology (BSSO) Foundry

The BSSOF includes many namespaces.

I recommend some kind of good-faith but strong evidence that a bespoke URL
base will continue to be maintained after funding ends

I agree. I suppose we need to assess what counts as "good-faith but strong evidence".

@shawntanzk shawntanzk added the attn: OFOC call Issue to discuss on fortnightly OBO Operations meeting label Jan 7, 2025
@ddooley
Copy link
Contributor

ddooley commented Jan 14, 2025

I'll say that a mini-project in an upcoming FoodOn hackathon is to create an RDF graph of geographical names and some geographical relations extracted from Wikidata/Wikipedia for use within FoodOn and GenEpiO, taking over from past use of GAZ. So this is a case where non-OBO purls will be offered to all on a script-driven github site I think. Hope that goes down well! The Wikidata "slim" will be offered to all. If this seems problematic let me know!

@cmungall
Copy link
Contributor

That sounds eminently sensible @ddooley. I don't know if there is a way for OBO to be meaningfully involved, this is more like what many of us do for conversion of biological knowledge bases

See:

@matentzn
Copy link
Contributor

Here is an importat warning story why never to use simple URLs for domain without a long term maintenance plan for IRIs:

#2425

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attn: OFOC call Issue to discuss on fortnightly OBO Operations meeting ontology metadata Issues related to ontology metadata
Projects
None yet
Development

No branches or pull requests

6 participants