The phone number format restriction seems problematic:<br><br>In Brazil a typical phone number would be <a href="tel:%2B55%2011%202204-7931" value="+551122047931" target="_blank">+55 11 2204-7931</a> (this is a guessed phone number from Brazil (55) in the city of São Paulo (11) in the neighbourhood of Tucuruvi (2204))<br>
<br>As you can see the format for brazil is +CCDDNNNNNNNN (C for country
code, D for state code, N for number) which corresponds to 12 digits
instead of 11 digits defined in the JSON struct<br><br>happy hacking,<br>Felipe "Juca" Sanches<br>
Garoa Hacker Clube<br>São Paulo, Brazil<br><a href="http://garoa.net.br/" target="_blank">http://garoa.net.br/</a><br><br><div class="gmail_quote">On Mon, Nov 21, 2011 at 7:14 PM, miloh <span dir="ltr"><<a href="mailto:froggytoad@gmail.com">froggytoad@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p>I'll be investigating the utility of this project and perhaps adding nb in. Any constructive comments on the proposal or ideas for things to build around a hackerspace status api?</p>
<div class="gmail_quote">---------- Forwarded message ----------<br>From: "Moritz Bartl" <<a href="mailto:moritz@hackerbus.eu" target="_blank">moritz@hackerbus.eu</a>><br>Date: Nov 21, 2011 1:01 PM<br>Subject: [hackerspaces] HackerSpace Status API – rel0.11<br>
To: <<a href="mailto:discuss@lists.hackerspaces.org" target="_blank">discuss@lists.hackerspaces.org</a>><br><br type="attribution">The HackerSpace Status API proposes a unified syntax to publish information about a hackerspace for consumption by javascript widgets, mobile apps and other scripts or programs. The API is flexible, and allows for custom extensions.<br>
<br>
The API is based on JSON, and defines the properties of the space status JSON object. In this specification, some fields are mandatory, whereas others are optional. A hackerspace implementing this API should at least provide the mandatory fields.<br>
<br>
<a href="http://hackerspaces.nl/spaceapi/" target="_blank">http://hackerspaces.nl/<u></u>spaceapi/</a><br>
<br>
Space directory<br>
<br>
The space status directory can be found on:<br>
<br>
<a href="http://chasmcity.sonologic.nl/spacestatusdirectory.php" target="_blank">http://chasmcity.sonologic.nl/<u></u>spacestatusdirectory.php</a><br>
<br>
To be included in this directory, please email the author of this document with your URL.<br>
<br>
Status object<br>
<br>
The JSON object has these fields:<br>
<br>
api (string, mandatory) – ’0.11′<br>
space (string, mandatory) – name of the hackerspace;<br>
logo (string, mandatory) – url to a png, jpg or gif image;<br>
icon (array, mandatory) – provides url’s to 2 icons to use to depict ‘open’ and ‘closed’ status:<br>
open (string, mandatory): url to a square png file with a max resolution of 100×100 pixels;<br>
closed (string, mandatory): url to a square png file with a max resolution of 100×100 pixels;<br>
url (string, mandatory) – url to the hackerspace homepage;<br>
address (string, optional) – visiting address;<br>
contact (object, optional) – has the following subfields:<br>
phone (string, optional) – phone number (in the form of +CCNNNNNNNNN, where CC is the countrycode);<br>
sip (string, optional) – sip uri (eg. ‘<a href="mailto:sip%3Agmc@pbx.sonologic.net" target="_blank">sip:gmc@pbx.sonologic.net</a>’<br>
keymaster (string or array of strings, optional) – phone number, or phone numbers of people able to open the space (for spaces where not all members can unlock the door<br>
irc (string, optional) – irc channel in the form of ‘irc://freenode/#revspace’;<br>
twitter (string, optional) – twitter account in the form of ‘@brenno’;<br>
email (string, optional) – general email address;<br>
ml (string, optional) – public mailing list address;<br>
jabber (string, optional) – jabber chatbox;<br>
…. – additional fields may be added if needed (but please let the author know, so it can be added to the spec in order to achieve consistency across implementations).<br>
lat (float, optional) – latitude<br>
lon (float, optional) – longitude<br>
cam (array of strings, optional) – webcam url(s);<br>
stream (array, optional) – object indexed by stream type with url to stream as value (eg { ‘mp4′:’http\/\/etc…’,'mjpg’:'…<u></u>.’})<br>
open (boolean, mandatory) – ‘true’ if the space is currently open, ‘false’ if not;<br>
status (string, optional) – additional free-form string to specify the ‘open’ status (ie, ‘open for public’, ‘members only’, …)<br>
lastchange (long int, optional) – seconds since epoch of last change in the open field;<br>
events (array, optional) – array of recent check-in/check-outs or other relevant events the space wants to share (such as the fire-alarm).<br>
Each entry in the events array has the following fields:<br>
name (string, mandatory) – name or nickname of person or object associated with this event;<br>
type (string, mandatory) – ‘check-in’ or ‘check-out’ (other values may be specified, but receivers of the object are not obligated to be able to understand these)<br>
t (long int, mandatory) – time since the epoch for this event<br>
extra (string, optional) – additional information<br>
______________________________<u></u>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.hackerspaces.org" target="_blank">Discuss@lists.hackerspaces.org</a><br>
<a href="http://lists.hackerspaces.org/mailman/listinfo/discuss" target="_blank">http://lists.hackerspaces.org/<u></u>mailman/listinfo/discuss</a><br>
</div>
<br>_______________________________________________<br>
Noisebridge-discuss mailing list<br>
<a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
<br></blockquote></div><br>