Starting to dig into these data APIs. I'm looking at a simple query for assets where I only change the data format of the response from XML to JSON. The docs state that for these two formats you will send back all asset fields. In the XML format I see the following fields for the search results...
search
time
totalResults
fromNum
toNum
page
However if I peak at the same query, but just the json format I see fields have different names for most of the objects in the results, but we'll just compare the first few fields of the results search parent object...
I assume we're pulling data from the same source, and just formatting the data to the requested format, but during that conversion are the resulting field names of these assets really different?
Im a little concerned to coding to one field naming schema to only have that changed moving forward.
I understand your concern with the JSON vs XML not matching. If we change it the fields to match, it will break for people currently expecting those fields.
This has not really been an issue before since most developers simply pick one or the other.
Starting to dig into these data APIs. I'm looking at a simple query for assets where I only change the data format of the response from XML to JSON. The docs state that for these two formats you will send back all asset fields. In the XML format I see the following fields for the search results...
search time totalResults fromNum toNum page
However if I peak at the same query, but just the json format I see fields have different names for most of the objects in the results, but we'll just compare the first few fields of the results search parent object...
search (implied) searchTime numberOfResults fromNum (omitted in json results) pageSize endIndex
I assume we're pulling data from the same source, and just formatting the data to the requested format, but during that conversion are the resulting field names of these assets really different?
Im a little concerned to coding to one field naming schema to only have that changed moving forward.
Thoughts?
Message edited by tfoust 12 years ago
Tags
jarredd – 12 years ago
Hi Todd,
I understand your concern with the JSON vs XML not matching. If we change it the fields to match, it will break for people currently expecting those fields.
This has not really been an issue before since most developers simply pick one or the other.
Best regards, Jarred