Why are the response formats for batch and single target response shown as being different in the API docs. Surely the batch response is really just an array of single target responses? The batch response has "sameAs" & "mappingRelation" which don't seem to be listed in the API docs but don't have "primaryTopic" for each response within the items array which of course means that writing parsers is made harder :(
Anyway, I just noticed that the chembl info now in the "mappingRelation" block. Why? For an example, look at the following URI http://www.conceptwiki.org/concept/00059958-a045-4581-9dc5-e5a08bb0c291 and the corresponding single:
and batch calls:
The different mapping predicates (sameAs, mappingRelation) as well as the other differences between batch calls and those for single entity are due to design limitations associated with RDF/SPARQL, since all API results are generated from RDF responses to SPARQL queries.
Clarifies that I don't understand SPARQL enough :) Why don't we just have the 'batch' call and remove the target info one. Target info would then just be a 'batch' call with 1 URI. Could do the same for compound info/batch.
Anyway, I still don't understand why the batch call isn't just multiple info calls. Still confused why the chembl bits don't appear in exactMatch. Are you implying that anything that can appear in an exactMatch block can appear in the mappingRelation part (singeton or array?) depending on what the URI is?