Syncing the raw query string seems like a bad idea since we can't really insulate ourselves from changes to how queries are constructed in Places. We should represent queries in abstract objects. Then whatever Sync code was written for the Places version in question can do the appropriate thing with the same data. This, for instance, will help us bridge the gap until stuff like bug 641671 is implemented. We might not even need to rev the bookmark storage version for this, we could probably just implement a new places type called "query2" or something. Old code (Firefox 4) will ignore it, new code will understand it.
You need to log in before you can comment on or make changes to this bug.