[bioontology-support] JSON format exception in new API

[Ray Fergerson]

Eric,

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.

Ray

-----Original Message-----
From: bioontology-support-bounces at lists.stanford.edu
[mailto:bioontology-support-bounces at lists.stanford.edu] On Behalf Of Erik
Fäßler
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

“description”:false

This is wrong of course since there it no ‘description’ field. I meant to
write

“definition”:false

Sorry for any confusion that might have caused.

Best,

Erik

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 don’t 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
>
> “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 lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/bioontology-support

_______________________________________________
bioontology-support mailing list
bioontology-support at lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/bioontology-support