-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments on first pass of syngo OWL #1
Comments
|
Just FYI, while ORCIDs are highly encouraged, they not actually a requirement of the system. |
@cmungall Re evidence model: This model has today's date on it and uses the old schema. So maybe I should keep it as_is and switch over when noctua does? |
New example output file in turtle format with import statement: https://github.com/geneontology/syngo2lego/blob/master/example_output/SynGO_132.ttl Only includes genuine OBO classes. Still includes Class declarations. If those are a problem, I need advice on how to get rid of them. |
You're right about the evidence property, I thought we'd made the switch. I agree about the declarations-imports. I would actually prefer we did it your way. I don't think your way will cause any problems. Note that the imports will be injected back in when we do the backup save to noctua-models, and also when it is retrieved in-memory from blazegraph. Primarily for aesthetic reasons, can we have the model/ontology IRI have no underscores and no ".owl" suffix? Really the only thing you need to conform to is having the URL start model.geneontology.org/ (this gets injected into the CURIE map at startup), but I think it's good to have consistency here. |
So can we have a go at loading it into noctua?
…On 27 Apr 2017 8:06 p.m., "Chris Mungall" ***@***.***> wrote:
You're right about the evidence property, I thought we'd made the switch.
I agree about the declarations-imports. I would actually prefer we did it
this way. I don't think your way will cause any problems. Note that the
imports will be injected back in when we do the backup save to
noctua-models, and also when it is retrieved in-memory from blazegraph.
Primarily for aesthetic reasons, can we have the model/ontology IRI have
no underscores and no ".owl" suffix? Really the only thing you need to
conform to is having the URL start model.geneontology.org/ (this gets
injected into the CURIE map at startup), but I think it's good to have
consistency here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAG4x-jeGarusNHi1obLDJehfwUHJ_1Cks5r0OcfgaJpZM4NJCaY>
.
|
I've dropped the .owl file extension. For parsing, it would be useful to keep a consistent separator between namespace and SynGO identifier. If not underscore, would a dash be OK? |
Make a PR with the files added here: https://github.com/geneontology/noctua-models/tree/master/models |
What will the dataflow be? We have no way to prevent edits on these models. Do they 'belong' to Noctua once added? |
It may be possible to add a "locked" annotation state. For now, it could be respected on the client; later, prevented from modification at the server end as well. |
|
Close, out of date? |
Think so. Looks like superseded by geneontology/noctua-models#55. Have no idea if this turned into an ongoing import. Would be a great shame if not. |
The following are not necessarily wrong, just observations of differences. cc @balhoff @kltm
Aside: Re: imports/declarations. This has always been awkward. In noctua-models we always store an import to go-lego.owl. This interferes with agile parsing using the OWLAPI (need to either load all of lego.owl or rewire to more minimal ontology using catalogs). But we either need this, or we need the declarations. Maybe this can be revisited now we are in blazegraph..
The text was updated successfully, but these errors were encountered: