[Spaceapi-devel] status field in 0.13

[slopjong]

On 2013-02-26 05:58, Roland Hieber wrote:
> Hey,
>
> I just tried to implement the 0.13 RC, but I found conflicting
> requirements about the "status" field.
>
> http://openspace.slopjong.de/specs/0.13 says, the field should be an
> object containing the properties "open" and an "icon" array
>
> http://hackerspaces.nl/spaceapi/ (and the GitHub repo) says, it 
> should
> be a text field.
>
> So, which of these pages is outdated? :-)

> As a side note, if we make the "status" field an array, we would 
> break
> backward compatibility. So I rather name it "state" instead.

There are multiple status-related fields that need to be combined in an 
object/array to improve the structure. By doing so we break the 
compatibility anyway, no matter we call it state or status. If a space 
calls it state, they won't have status (except they make things 
redundant) and thus they won't work with old webapps anymore.

[...] half of email lost due to a too small webmail timeout, my space 
is either too restrictive or incompetent >:( [...]

I make it short this time as it's really stupid to do things more than 
once:

* until now the version number increased already when just a new webapp 
got listed on hackerspaces.nl.
* people interpret version number as 'specification has changed' and 
wonder if there's suddenly v0.17 after v0.12.
* v0.13 on hackerspaces.nl is in fact v0.12
* v0.13 in OpenSpaceLint is not RC yet. New fields might be necessary 
for certain features.
* OpenSpaceLint clearly says "This is still a draft, see the changelog" 
and the changelog flags v0.12 stable and v0.13 to be a draft.
* hackerspaces.nl is outdated, openspace.slopjong.de/specs/0.13 is 
relevant as it's used to validate

I hope this clarified things :-)

Cheers,
slopjong