[Spaceapi-devel] 0.13 suggestions

[Andrew Elwell]

As 0.13 introduces some backwards-incompatible changes, can I suggest
we just bump the major version rather than piddling around with
0.12,0.13 etc

I'm basing this on what we see in big REST sites - plan being so that
GET http://example.org/spaceapi/1/status should return json tied to
that version of the API - ditto if some app could only understand 0.12
syntax


it means a site can update both (or have some dynamic script that can
return the correct version depending how it was called) and not break
things in the meantime

If a site also did some oauth (or equvalent) voodoo there's the chance
that a public status feed would be different to what's shown to
members -- ie webcam feeds, events (*who* last opened the door etc)
rather than just an open/closed flag

so -- what's the best way to contribute to this? I've thrown a couple
of pull requests on github (one minor to add an optional 'spacefed'
boolean if the space supports federated identity logins and another to
bump the example in devel so that it actually verifies against the
0.13 proposal

Andrew