Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[bioontology-support] JSON format exception in new API

Ray Fergerson ray.fergerson at
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.


-----Original Message-----
From: bioontology-support-bounces at
[mailto:bioontology-support-bounces at] On Behalf Of Erik
Sent: Monday, October 28, 2013 12:57 AM
To: support at
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> wrote:

> Dear support team,
> I just wanted to report a case where the value of a field was of an
unexpected type. I don’t whether this is intended; I rather think this
could be filtered server-side.
> The class with ID of the
NIFSTD ontology specifies
> “description”:false
> 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,
> Erik
> _______________________________________________
> bioontology-support mailing list
> bioontology-support at

bioontology-support mailing list
bioontology-support at

More information about the bioontology-support mailing list