Are there any plans for dealing with data versioning? I assume that the schema won't stay exactly the same forever, so I was wondering how this will be handled?
I'm certainly not near the point where I have to worry about this, but it would be nice for my app to at least acknowledge if Toodledo is responding with a newer version of the data than my app can handle.
Our intention is to maintain backwards compatibility. If you are using a proper XML parser to read the API data, then you shouldn't have a problem. If you are relying on structural details (like the due-date field is always immediately followed by the due-time field), then you may have problems.
If we ever have to change the API in a backwards incompatible way, what we will do is make a separate API so that we don't break the old one.