[Interop-dev] Network Device JSON Schema

Moritz Warning (spam-protected)
Sun Oct 26 11:50:09 CET 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I guess that ventures too munch into the meta domain.
Let's first try to get to a common ground without. :-)

On 10/26/2014 11:15 AM, Mitar wrote:
> Hi!
> 
> One crazy idea. We could define JSON-LD as schema. JSON-LD is an
> interesting approach because it makes defining schemas much easier. One
> does not have to agree on how field names are named, but only on
> semantics of values. And then you can name your fields as you want and
> you define what each field represents. And then there are programs to
> translate between.
> 
> 
> Mitar
> 
>> For what it matters, we use this rather minimal format:
>>
>> {
>> 	"name" : "foobar",
>> 	"firmware" : "ffbi-0.3",
>> 	"community" : "somecity",
>> 	"geo" : "52.02513078 8.55887",
>> 	"links" : [
>> 		{ "smac" : "b0:48:7a:f6:85:76", "dmac" : "8c:21:0a:d8:af:2b", "qual" : 251 }, 
>> 		{ "smac" : "2a:88:01:80:6b:93", "dmac" : "ee:51:43:05:1f:ef", "qual" : 255 }
>> 	],
>> 	"clientcount" : 2
>> }
>>
>> On 10/26/2014 03:34 AM, Nemesis wrote:
>>> Hi everyone,
>>
>>> recently I met some of you guys and girls and I think there's the shared
>>> opinion that we should get back together and collaborate on small tasks,
>>> which should not be so painful as working on big tasks.
>>
>>> One small task that has been in the backlog for some time was this JSON
>>> representation ofa network device.
>>
>>> I sat together with Andi (Freifunk Weimar) today at the Google Mentor
>>> Summit Reunion, we compared a few JSON outputs: openwifi map, openwrt
>>> ubus, netengine and we came up with afirstbasic proposal.
>>
>>> We haven't worked on the JSON schema yet, only on an example, it should
>>> be easy to write the JSON schema after we agree on some examples.
>>
>>> So I would like to encourage all of you to take a look atthis file:
>>> https://github.com/interop-dev/network-device-schema/blob/master/example.json
>>
>>> Our aim is to include only the very essential bitsand then start
>>> iterating to improve it.
>>
>>> What do you think?
>>
>>> Federico (Ninux) and Andi (Freifunk)
>>
>>
>>
>>> _______________________________________________
>>> Interop-dev mailing list
>>> (spam-protected)
>>> https://lists.funkfeuer.at/mailman/listinfo/interop-dev
>>
>>
>>
>> _______________________________________________
>> Interop-dev mailing list
>> (spam-protected)
>> https://lists.funkfeuer.at/mailman/listinfo/interop-dev
>>
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBCAAGBQJUTNHhAAoJECHrh56PP4wpHO0H/AtbkNVcYBtUczXtZpeFc5zX
EvhPy5xUS61vc4tbcFBbJCCSMw+kRnNw4CkknZJM/d0GhJEU2HUriL3J0B8C5jcy
mNm3voopWtKXyCN9Wtr+b9Qs9hInSTPj6tePM4RSHaoPXhE16/hd+giqkXXrV4v+
8CXMW/UFVq2zp6b50oQH0Jfl5UCubGbEyhsXoVdFNUSIMVyM5DFl8uOFJQZhAHNE
DayAhix9dGzqsUJYBmfQbNPVgz1Ded1zNBUTkRaU5niRnloM/8ltyVFrXoNK2ITz
7DSMpsBWm/Dov717HSKjtUoDTb0wGunCQguWvYXzn8nY7qh8087bXF1rYwRrR+0=
=svFU
-----END PGP SIGNATURE-----




More information about the Interop-dev mailing list