Sign in to get statistics for your attended concerts! (Hide)
    • gshackles
    • Question about cities schema

    • May 9, 2011 12:38:38 AM UTC

    When you look up a city by ID, you get an XML result with a single “city“ element. However, when you do a search for cities (for example: http://api.setlist.fm/rest/0.1/search/cities?name=new%20york&country=us) you get a root element of “cities“, and then each child element is also named “cities“. I realize this is how it is specified in the docs (http​://ap​i.set​list.​fm/do​cs/da​ta_ns​0.htm​l#ele​ment_​citie​s) but is there any reason for this? It seems to me that nesting “city” elements would make more sense, and would simplify deserialization of the results as well.

    • fuzy
    • Re: Question about cities schema

    • May 9, 2011 7:01:37 AM UTC

    Hi Greg,

    you‘re absolutely right. Unfortunately it‘s difficult to change it now as it could break working implementations. It‘s certainly on the TODO for the next version though.

    Cheers, Stefan

    • gshackles
    • Re: Question about cities schema

    • May 9, 2011 11:06:08 AM UTC

    Awesome, thanks for the update! Any idea when the next version will drop?