[WLANnews] JSON data interchange format for networks

[Monic Meisel]

Liebe Node-Daten Bastler - FYI 

> Hi everybody,
> 
> in the past 2 months some people have been working on a simple idea, which would bring a lot of benefits to many people and that for some strange reason has not been implemented yet, probably because the effort is more "human" than technical, as many different people have to work together and come to agreements.
> 
> But here's the idea:
> 
> Immagine you could export a device configuration in JSON format and reimport that somewhere else, like monitoring software, node database, or whatever you need.
> Something like this: https://github.com/interop-dev/json-for-networks/blob/master/examples/device-configuration.json
> 
> Immagine you could extract monitoring data with a simple JSON that has a similar structure to the device configuration, that would enable different software to play well with one another, instead of building silos that don't talk to each other.
> Something like this: https://github.com/interop-dev/json-for-networks/blob/master/examples/monitoring-data.json
> 
> Immagine the olsr json info plugin, or the json output by batman, but instead of being all different, they shared a common structure, and differed only in the key/value pairs that are specific to their protocol.
> That would be easier to parse for who develops software to represent those topologies visually.
> Something like this: https://github.com/interop-dev/json-for-networks/blob/master/examples/network-routes.json
> 
> Now, this is not some weird utopic idea. A similar thing has been done in the GIS field: GeoJSON.
> You can pass GeoJSON to any GIS library, written in any language, and it will understand what                                                         is that you are passing. You can visualize that GeoJSON on a map with leaflet or openlayers, you can use it to calculate distances and stuff on the server side, you can output on an HTTP API, or whatever.
> 
> Here there's a very early draft of the spec:
> https://github.com/interop-dev/json-for-networks
> 
> Before we start implementing it in softwares like node databases, monitoring systems and firmwares, we would love to have some feedback from the battlemesh community, especially the routing protocol developers.
> 
> We would like to know if anyone else has been working on a similar idea and we would like to have constructive critical feedback and improve our early spec before starting to prototype.
> 
> If anybody will be at Fosdem we can also discuss in person there.
> 
> Cheers to all and hope to see many of you at the next battlemesh in Slovenia.
> 
> Federico Capoano (aka Nemesis)
> Ninux.org
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
-------------- nächster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.freifunk.net/pipermail/wlannews-freifunk.net/attachments/20150110/e05542a6/attachment-0001.html>
-------------- nächster Teil --------------
Ein Dateianhang mit Binärdaten wurde abgetrennt...
Dateiname   : smime.p7s
Dateityp    : application/pkcs7-signature
Dateigröße  : 5867 bytes
Beschreibung: nicht verfügbar
URL         : <http://lists.freifunk.net/pipermail/wlannews-freifunk.net/attachments/20150110/e05542a6/attachment-0001.bin>