-
Notifications
You must be signed in to change notification settings - Fork 0
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
Include shapes for models/graphs #252
Comments
@cmungall we do have the start of this in the schema now. e.g. it specifies that models should have exactly one title
|
ah cool, was looking at an older version
so if we run this over the public triplestore all the inferred models will
be marked invalid (same if we adopt a caching reasoner strategy for the
curation store)
it's also confusing if we use shex as documentation for end-user developers
any ideas how to handle this? Two separate GoCamModel classes?
…On Mon, Nov 16, 2020 at 4:00 PM goodb ***@***.***> wrote:
@cmungall <https://github.com/cmungall> we do have the start of this in
the schema now. e.g. it specifies that models should have exactly one title
<GoCamModel> {
a [owl:Ontology] + ;
contributor: xsd:string +; #TODO would be better as an IRI
date: xsd:string {1}; #TODO can we make this an xsd:date?
provided_by: xsd:string +; #TODO would be better as an IRI
rdfs:comment xsd:string *;
modelstate: xsd:string {1}; #TODO would be better as an IRI
in_taxon: . *;
title: xsd:string {1};
imports: . *;
oboinowlid: . *; #TODO not sure if we really want this?
owl:versionIRI . *;
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#252 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMMON27OHAI37FCVJ4W6DSQG4JLANCNFSM4TX273TA>
.
|
current count of model properties (on public store):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should include shapes for the model itself.
I think we should make all assumptions explicit. E.g. should every model have a title? a status?
Should we have separate shapes for a curated model vs the named graphs we use to cache inferences (cc @balhoff @dougli1sqrd )?
here is a model chosen at random
here is it's corresponding inferred graph:
todo: compare with a reactome-derived graph @goodb
Do we have a more explicit way to tell if a graph is inferred other than checking if a derivedFrom triple is there? Is this a guarantee, e.g. might we have derivedFrom on the main models in future (e.g. derived from a template?)
The text was updated successfully, but these errors were encountered: