URIs

[jonathanbona]

The ontology IRI http://purl.obolibrary.org/obo/radont.owl is used for the legacy file in our repository (https://github.com/aapm-bdsc-ontology-tg/radont/blob/master/radont.owl)

The OBO-compliant prefix used in that file is http://purl.obolibrary.org/obo/RADONT_, so term identifiers would be http://purl.obolibrary.org/obo/RADONT_0000001, etc.

I propose that we reserve and use http://purl.org/rto-draft as the base URI for now while we get the basic structure in place, then request from OBO, and switch to, http://purl.obolibrary.org/obo/RTO

If there is general agreement on the placeholder purl for drafting, it would take me just a minute to reserve http://purl.org/rto-draft

[Bayesianworld]

I agree that this is the right policy.

[andredekker]

The legacy file is actually not a legacy one but meant to be the one we are developeing. So we could use http://purl.obolibrary.org/obo/RADONT_ and radont.owl

RTO is not the best choice as there is already an ontology named RTO and that is confusing

OK with the drat.

From: Jonathan Bona notifications@github.com Sent: Friday, January 31, 2020 19:07 To: aapm-bdsc-ontology-tg/radont radont@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [aapm-bdsc-ontology-tg/radont] URIs (#4)

The ontology IRI http://purl.obolibrary.org/obo/radont.owl is used for the legacy file in our repository (https://github.com/aapm-bdsc-ontology-tg/radont/blob/master/radont.owl)

The OBO-compliant prefix used in that file is http://purl.obolibrary.org/obo/RADONT_, so term identifiers whould be http://purl.obolibrary.org/obo/RADONT_0000001, etc.

I propose that we reserve and use http://purl.org/rto-draft as the base URI for now while we get the basic structure in place, then request from OBO, and switch to, http://purl.obolibrary.org/obo/RTO

If there is general agreement on the placeholder purl for drafting, it would take me just a minute to reserve http://purl.org/rto-draft

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/aapm-bdsc-ontology-tg/radont/issues/4?email_source=notifications&email_token=AAR2UIX556BVWWCSWK4BZY3RARSDLA5CNFSM4KOLFPQKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IKGXN2A, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAR2UIU26ZVFHE5QQ3AM5GTRARSDLANCNFSM4KOLFPQA.

[Bayesianworld]

Looks like Andre is right about an already-existing ontology: DBMS Real Time Ontology (RTO). I think when we discussed this a few months ago, they had not published anything so RTO sounded good. While I think a DBMS ontology for real time access is a bit lame :) , I guess there is not much we can do about that now.

[jonathanbona]

http://purl.org/rto-draft now redirects to https://github.com/aapm-bdsc-ontology-tg/radont and I have set up my Protege preferences to generate URIs of the form http://purl.org/rto-draft#RADONT_xxxxxxx

Here is what that configuration looks like in Protege:

[andredekker]

In the current file there is still a mix of :RADONT and RADONT_. This needs to be bulk-fixed.