Search Mailing List Archives
[bioontology-support] JSON format exception in new API
ray.fergerson at stanford.edu
Wed Nov 6 16:22:19 PST 2013
It appears that this ontology does have the comment/definition for that
term ("obsolete adductor") set to "false". This is probably an ontology
error as similar terms all have meaningful definitions. I suggest
contacting the ontology authors and pointing this problem out.
From: bioontology-support-bounces at lists.stanford.edu
[mailto:bioontology-support-bounces at lists.stanford.edu] On Behalf Of Erik
Sent: Monday, October 28, 2013 12:57 AM
To: support at bioontology.org
Subject: Re: [bioontology-support] JSON format exception in new API
Some correction to my own mail.
I wrote the error happened at
This is wrong of course since there it no description field. I meant to
Sorry for any confusion that might have caused.
On 25 Oct 2013, at 17:01, Erik Fäßler <erik.faessler at uni-jena.de> wrote:
> Dear support team,
> I just wanted to report a case where the value of a field was of an
unexpected type. I dont whether this is intended; I rather think this
could be filtered server-side.
> The class with ID http://purl.obolibrary.org/obo/UBERON_2000463 of the
NIFSTD ontology specifies
> where I expected to be an array of strings. In all other cases I had
seen, the value of the description field is an empty array in case there
is no description. The boolean false value crashed my JSON parsing.
> Just wanted you to know, I will try and handle this in my code.
> Best regards,
> bioontology-support mailing list
> bioontology-support at lists.stanford.edu
bioontology-support mailing list
bioontology-support at lists.stanford.edu
More information about the bioontology-support