Replying to bits of two of Dominic's mesages:
Rather than having the central portal accept edits itself, it should present the user with a choice of relevant guides to add to:
I would rather keep the UI simple, I dont imagine that peoples comments are sent imediately, though I wouldnt stop them, but rather have the client code store up a batch of changes which are uploaded at once, along with any blog posts, gsm cell id to location mappings, osm map corrections etc. So I want a fire and forget API (well a msg accepted/failed response is ok).
..maybe there is also a need for a global OpenGuide that can be used as a place to store such things.
Yep that would be fine, and any new ambigous articles can go there and then be adopted by new or existing local guides as relivant, or live on the global one if not, which would always have to be asked for articles when the mobile app requests articles for a specific bbox.
I don't quite understand what you're getting at here; what, technically is required that isn't already provided by OpenGuides? Is it just a case of mobile-friendly stylesheets?
Just that I personally dont do remote web access unless I have to, I use a PAYG sim when out and about, and then free WiFi (at home or where I find it) to sync up any larger activities. If I had an all you can eat tarrif then I might be more inclined to do things like edit web pages online. Also my app uses a compressed binary protocol for communicating to my server (acting as a proxy) so saving costs over using a normal bloated html/xml.
Cheers,
Adam.