<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi again everybody,<br>
<br>
I'm really sorry to bother you again, but we would have really
loved to hear back from you.<br>
<br>
Even offlist if you don't want to bother all the subscribers.<br>
<br>
If anyone can help us, it will be very useful for many people.<br>
<br>
Thank you again.<br>
Federico<br>
<br>
<br>
On 11/27/2014 11:05 AM, Nemesis wrote:<br>
</div>
<blockquote cite="mid:5476F752.8070109@ninux.org" type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<font face="Helvetica, Arial, sans-serif">H<font face="Helvetica,
Arial, sans-serif">i everyone,<br>
<br>
<font face="Helvetica, Arial, sans-serif">first of all, I want
to thank you for putting effor<font face="Helvetica, Arial,
sans-serif">t in creating this a<font face="Helvetica,
Arial, sans-serif">wsome </font>open standard.</font></font><br>
<br>
<font face="Helvetica, Arial, sans-serif">I started working
with it just<font face="Helvetica, Arial, sans-serif"> at
the beginning of 2013</font></font>, and soon after I
understood <font face="Helvetica, Arial, sans-serif">why this
is <font face="Helvetica, Arial, sans-serif">amazing<font
face="Helvetica, Arial, sans-serif">: it could make GIS
<font face="Helvetica, Arial, sans-serif">libraries
written in comp<font face="Helvetica, Arial,
sans-serif">letely different</font> languages
interop<font face="Helvetica, Arial, sans-serif">erable,
making it easy to develop and share bits of reusable
code</font></font></font></font></font>, it created
an ecosystem<font face="Helvetica, Arial, sans-serif"> and
then finally even <font face="Helvetica, Arial, sans-serif">github
implemented it so that geojson files would be displayed as
maps.<br>
<br>
<font face="Helvetica, Arial, sans-serif">Working <font
face="Helvetica, Arial, sans-serif">a lot in<font
face="Helvetica, Arial, sans-serif"> the networking
field, I wondered: why there's no standard JSON
format to represent common<font face="Helvetica,
Arial, sans-serif"> network<font face="Helvetica,
Arial, sans-serif">ing tasks<font
face="Helvetica, Arial, sans-serif"> l<font
face="Helvetica, Arial, sans-serif">ik<font
face="Helvetica, Arial, sans-serif">e <font
face="Helvetica, Arial, sans-serif">configuration
of devices, routing protocols
topologies, monitoring data? A </font></font></font></font></font>JSON
for networks like</font> GeoJSON</font></font></font>
is for GIS.<br>
<font face="Helvetica, Arial, sans-serif">Developing <font
face="Helvetica, Arial, sans-serif">web app<font
face="Helvetica, Arial, sans-serif">s that deal with
network<font face="Helvetica, Arial, sans-serif">s
is terribly painful. Why it has to be like that?</font></font></font></font><br>
<br>
<font face="Helvetica, Arial, sans-serif">So I started
talking about this at the Google Summer of Code Reunion<font
face="Helvetica, Arial, sans-serif"> 2014 <font
face="Helvetica, Arial, sans-serif">in San J<font
face="Helvetica, Arial, sans-serif">ose </font></font>with
some other peers and friends, we liked the idea</font></font>
and we started working via mailing list and then I f<font
face="Helvetica, Arial, sans-serif">inally tr<font
face="Helvetica, Arial, sans-serif">ied to put a first
draft <font face="Helvetica, Arial, sans-serif">on
this repo: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://github.com/interop-dev/json-for-networks">https://github.com/interop-dev/json-for-networks</a><br>
<br>
<font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif">I'm here
to ask <font face="Helvetica, Arial,
sans-serif">you a few questions<font
face="Helvetica, Arial, sans-serif">,
hoping that you can share with us some of
your experience.<br>
</font></font></font></font></font></font></font></font></font></font></font></font>
<ul>
<li>how much time passed between the first idea and the first
implementation?</li>
<li>how much time passed between the finalization of the spec
and the RFC?</li>
<li>were there conflicts while defining the spec? If yes, do you
have any suggestion for us in case it happens for us too?<br>
</li>
<li>how can we encourage others to implement the new format in
their projects? How did you achieve this?</li>
<li>are there mistakes you did that you can share with us?
Things to avoid at all costs?</li>
<li>are there suggestions you want to share with us? <br>
</li>
</ul>
<font face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif"><font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif"><font face="Helvetica, Arial,
sans-serif"><font face="Helvetica, Arial, sans-serif">Thank
you very much for your attention<font
face="Helvetica, Arial, sans-serif">.</font><br>
<font face="Helvetica, Arial, sans-serif">Best
regards<br>
<font face="Helvetica, Arial, sans-serif">Federico
<font face="Helvetica, Arial, sans-serif">Capoano</font></font><br>
</font></font></font></font></font></font></font></font>
</blockquote>
<br>
</body>
</html>