hello jan.
Jan Algermissen wrote:
On Aug 28, 2010, at 8:28 PM, Erik Wilde wrote:
no, we're building an API (targeted on spatial information services) and for
our demos we need something that is a UI, but the API should be equally useful
for machine-to-machine scenarios as it is for UIs.
Can you provide an example of a m2m use? (would greatly help to wrap my brain
around other stuff I am currently doing).
since we're building on atom and atompub, you can simply look at atom's
canonical "blogging" use case. if you build a mobile client for creating
location-based information (let's say, snapping geotagged pictures with
some app that accesses our API), it would use our API to POST new
pictures (in that case the accepted media type might be JPEG instead of
some KML geometry), and to GET other pictures (such as your friends
snapping pictures). we are not in any way restricting the way in which
this app's UI would be built (or whether it even had a UI or would be
some fully automated app with no UI at all), we are only concerned with
the API design for LBS-oriented collections.
cheers,
dret.
