Discussion: updating all IRIs to be in the OBO purl style

[allysonlister]

You can see an original discussion about this recently here: OBOFoundry/OBOFoundry.github.io#2307

A copy of the comment from @cmungall in that thread

That would be a question for EBI, as they are in control of http://www.ebi.ac.uk/swo/

or you could simply make a new release of SWO at the old namespace consisting solely of obsolete URIs with term-replaced-by to the new ones. There is potential for confusion here though.

But the more disruptive part is that users of SWO who don't use CURIEs will have to update all their URIs. There are tools to do this but this may still be a big upheaval if the ontology has been widely used.

Before embarking on this big change I'd recommend seeking clarification on a few questions:

can exceptions to PURL policy be made on the OBO side? I would say yes, given that we already accepted the ontology, it's unreasonable of us to suddenly say, "oh we made a mistake and didn't check your PURLs, now make this hugely disruptive change or you're out", but there may be other perspectives
does using OBO PURLs provide any advantages to your users or you as a maintainer? (I can see some maintenance advantages in that you are not tied to EBI)
Does being listed in the OBO site give you any advantages, or is SWO happy to sit to the side? If the former then I'd start seeking clarification on your license issue too....

We can discuss here, but would prefer any discussion to happen in the thread above; this ticket is to make sure that it doesn't fall of our radar, and when a decision is reached we will add it here to keep track of what was decided.

[ddooley]

The OBI curation team has an item that is dependent on this: obi-ontology/obi#1175 OBI would migrate its software terms to a robot table managed over on SWO side. Is the robot table project going to be a separate issue?

[ddooley]

Any update on the use of robot for software names?

[allysonlister]

My apologies for the delay - SWO is developed on a "best effort" basis as there is no dedicated funding.

Last year we moved completely to the ODK/robot build procedure, which makes it a lot easier to create new releases for people who are already familiar with ODK.

Please can you remind me where we stand? From the OBI ticket, it looks like you have some software terms that you'd like SWO to pull from a table that robot can incorporate into SWO? Or do you want all of SWO into a table such that you can contribute to a SWO release via a table/spreadsheet?

It's my own fault, as I've left this longer than intended. Please let me know and we'll get this done :)