Information API call requires attributes in lower case
In my attempts to get the /information API call to work, I have finally figured it out: I must switch my entity names to lower case before sending them. This took me off guard because the /connections API call works regardless of case. Similarly, the /analogies API call works regardless of case.
I suggest consistency across the various API calls. Either be case insensitive or case sensitive. (Or when deviating, please document it.)
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Anthony Edwards on 03 Nov, 2010 08:15 PM
I also observed that /information API does not tolerate the "_" as a replacement for the space character. If a space character is in the attribute name, it must be present when calling /information.
Support Staff 3 Posted by Jim Fleming on 05 Nov, 2010 11:14 PM
Thanks Anthony, same issue as networks. I will open another issue for this as well.
/Jim
4 Posted by Jared Peterson on 20 Jan, 2011 04:41 PM
Ok, after looking into this I don't think we want to change this. Forcing lowercase of values is dangerous. The reason it works on the /connections call is because it passes through AQL which allows "looser" matching. On this call you're more explicitly targeting a memory.
We should just document this difference.
Jared Peterson closed this discussion on 20 Jan, 2011 04:41 PM.