-
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
Removed some unnecessary RDF properties #87
Conversation
While we need this in JSON, we probably don't need to include this in RDF (see #78). If we do need to insert it, we can add it back pretty easily.
We previously used this for letting JPhyloRef know when a phyloref was malformed, but it no longer checks this property -- it now just throws an error if reasoning fails.
testcase:internal_specifier
and testcase:external_specifier
BTW we might consider using |
Or perhaps you are suggesting that we record the internal and external specifiers using subclass statements, such as by describing the phyloref Alligatoridae as a subclass of I have opened an issue for converting the |
We can discuss this at the next call, but I didn't think this what we wanted Phyx to look like, right? (As opposed to the generated OWL expressions) |
Sounds good, I'll put it on the agenda! |
Instead, it returns the full component class the first time it is called, and subsequently returns an ID to that component class.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good as far as I understand 😉
This PR removes some RDF properties from the JSON Schema:
internalSpecifiers
andexternalSpecifiers
properties in JSON, we probably don't need to include them in RDF (see Figure out what to do about the top-level object in a Phyx file #78, An object property for associating an internal specifier with a phyloreference phyloref-ontology#7, An object property for associating an external specifier with a phyloreference phyloref-ontology#8). If we change our mind later, we can add them back pretty easily.malformedPhyloreference
field to let JPhyloRef know when a particular phyloreference was malformed (such as when it had no internal specifiers, or if one of its specifiers could not be mapped to a particular phylogeny node). JPhyloRef no longer checks this field at all, so we might as well remove it from here as well.subClasses
field (which is the@reverse
ofrdfs:subClassOf
).#phyloref1
had 4 component classes, the first component class for#phyloref2
would be identified as#phyloref2_component5
). I've changed this so that each phyloreference's component classes start counting from 1.Closes #78.