Status of RNAO project

[althonos]

Hi!

Currently, RNAO is listed as active on the OBO Foundry, but it has not been updated in 9 years, and contains many errors in both the OBO (unescaped quotes, odd relation semantics) and the OWL product (cardinality errors mostly). It can't be opened by robot because of these issues, so I tend to think it is virtually unusable. Should it be listed as inactive ?

cc @cmungall
cc @AntonPetrov

[cmungall]

I support this, but cc-ing @leechuck and @micheldumontier who were involved in its construction

I think it's good practice to open an issue about the errors in the respective tracker: https://github.com/BGSU-RNA/rnao/issues (even though the tracker doesn't look very active).

Note that an 'inactive' status doesn't indicate anything about quality of the ontology - I think RNAO is a high quality formalization of RNA structural biology, but it doesn't appear to be actively maintained.

I also wonder if the content has been superseded by the ncrno cc @Huang-OMIT

[AntonPetrov]

I will point this out to the BGSU RNA team that hosts the repo and see if they have any input.

[althonos]

I opened the following issues in the RNAO repo:

• Unescaped quotes in rnao.obo BGSU-RNA/rnao#2: Unescaped quotes in rnao.obo
• Unreachable RO import caused by outdated URL BGSU-RNA/rnao#3: Unreachable RO import caused by outdated URL
• Duplicate annotations in rnao.owl  BGSU-RNA/rnao#4: Duplicate annotations in rnao.owl
• Typedefs imported from RO should be refered to using xrefs BGSU-RNA/rnao#5: Typedefs imported from RO should be refered to using xrefs
• Make RNAO:1000300 obsolete BGSU-RNA/rnao#6: Make RNAO:1000300 obsolete

[Huang-OMIT]

@cmungall Chris: I agree with you: most of the content in RNAO has been superseded by the ncro ontology.

[cmungall]

I emailed some of the original RNAO developers and will report back.

[nlharris]

any word from the RNAO developers?

[leechuck]

To the best of my knowledge, RNAO development is inactive; I have not been involved in RNAO for several years. I support moving it to inactive; it can be activated again once the issues have been resolved and the old dev team or a new team continues the development.

[Huang-OMIT]

Agree.

[rvita]

Colin Batchelor is the one who was giving me updated info on rnao as of last year: [email protected]
@batchelorc

[cmungall]

ok, we are agreed - mark as inactive

…

[batchelorc]

I agree. From: Chris Mungall <[email protected]> Sent: 22 April 2020 03:07 To: OBOFoundry/OBOFoundry.github.io <[email protected]> Cc: Colin Batchelor <[email protected]>; Mention <[email protected]> Subject: Re: [OBOFoundry/OBOFoundry.github.io] Status of RNAO project (#867) ok, we are agreed - mark as inactive

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#867 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAIYINJXNC3G5AZZCRGKBIDRNZGN3ANCNFSM4HJZCHQQ>. This communication is from The Royal Society of Chemistry, a company incorporated in England by Royal Charter (registered number RC000524) and a charity registered in England and Wales (charity number 207890). Registered office: Burlington House, Piccadilly, London W1J 0BA. Telephone: 0207 4378 6556, Facsimile: 0207 4490 3393 (Head Office). This communication (including any attachments) may contain confidential, privileged or copyright material. It may not be relied upon or disclosed to any person other than the intended recipient(s) without the consent of The Royal Society of Chemistry. If you are not the intended recipient(s), please (1) notify us immediately by replying to this email and delete all copies from your system and (2) note that disclosure, distribution, copying or use of this communication is strictly prohibited. Any advice given by The Royal Society of Chemistry has been carefully formulated but is necessarily based on the information available, and The Royal Society of Chemistry cannot be held responsible for accuracy or completeness. In this respect, any views or opinions presented in this email are solely those of the author and may not represent those of The Royal Society of Chemistry. The Royal Society of Chemistry owes no duty of care and shall not be liable for any resulting damage or loss as a result of the use of this email and/or attachments. The Royal Society of Chemistry acknowledges that a disclaimer cannot restrict liability at law for personal injury or death arising through a finding of negligence. The Royal Society of Chemistry does not warrant that its emails or attachments are Virus-free: Please rely on your own screening.