From (spam-protected) Sat Nov 28 15:55:33 2009 From: (spam-protected) (L. Aaron Kaplan) Date: Sat, 28 Nov 2009 15:55:33 +0100 Subject: [Nodedb-interop] test Message-ID: test From (spam-protected) Mon Nov 30 20:46:52 2009 From: (spam-protected) (Mitar) Date: Mon, 30 Nov 2009 20:46:52 +0100 Subject: [Nodedb-interop] Let's start Message-ID: <4B14212C.60604@tnode.com> Hi! We have prepared documentation for our schema. It is available here: http://wlan-lj.net/wiki/Podrobnosti/NodeWatcher/Schema I think the important thing is to define globally unique IDs for all nodes in all systems which would not change during a lifetime of a node. We are using UUIDs to achieve this. In this way it is not just possible to interchange code/modules but also data about nodes. So there could be someday also aggregating system for all our systems (for example a global map of all nodes). I could fork our schema documentation and it could start as a schema draft where everybody would start adding your fields and discuss names of common fields. We can use our wiki for that if you wish. I think it would be also useful to invite also other wireless networking groups to this. Especially overseas ones. What do you think? Mitar From (spam-protected) Mon Nov 30 20:56:15 2009 From: (spam-protected) (Mitar) Date: Mon, 30 Nov 2009 20:56:15 +0100 Subject: [Nodedb-interop] Let's start In-Reply-To: <4B14212C.60604@tnode.com> References: <4B14212C.60604@tnode.com> Message-ID: <4B14235F.1030707@tnode.com> Hi! > We can use our wiki for that if you wish. Or we could setup a smaller site/wiki for "interop" specific things, where we would write down things like schema, publish links to our source code repositories, and also maybe use it for IP allocations list/cooperation. We could setup/host this. Mitar From (spam-protected) Mon Nov 30 21:30:32 2009 From: (spam-protected) (Mitar) Date: Mon, 30 Nov 2009 21:30:32 +0100 Subject: [Nodedb-interop] Let's start In-Reply-To: <4B14212C.60604@tnode.com> References: <4B14212C.60604@tnode.com> Message-ID: <4B142B68.6000401@tnode.com> Hi! > http://wlan-lj.net/wiki/Podrobnosti/NodeWatcher/Schema Ups, working URL is: http://wlan-lj.net/wiki/Podrobnosti/Nodewatcher/Schema Mitar From (spam-protected) Mon Nov 30 22:59:09 2009 From: (spam-protected) (Ramon Roca) Date: Mon, 30 Nov 2009 22:59:09 +0100 Subject: [Nodedb-interop] Let's start In-Reply-To: <4B14212C.60604@tnode.com> References: <4B14212C.60604@tnode.com> Message-ID: <4B14402D.6010506@guifi.net> Hi Mitar, thanks for your enthusiasm ;) You can check our data in XML (we call it CNML as for Communities Network Markup Language) using the "CNML" link provided at the bottom page on each zone at our network. As en example, for a zone of about 1,400 nodes: * http://guifi.net/en/planavic At the bottom, the CNML link drives you to: * http://guifi.net/en/guifi/cnml/8349 From there you can export all the information at several levels of depth. We're now just delivering the XML. By looking into this you'll see very much which objects are decribed and with which attributes. To help documenting it, we can use some tools looking at a valid XML code like: * http://www.hitsw.com/xml_utilities/ With that, you can currently get the XML schema and DTD provided below at this email. By looking into this you will see that there is an object hierarchy which migh be very much generalistic, basically and as a summary. * network o zones + child zones (up to n) # locations * devices o radios + interfaces # links By looking into the schema you provided, I do see there that you are very much describing a location, a device and a radio (all at the same object). To split between objects might be usefull for allowing a much more flexible description (a location might have several devices, a device might have several radios, an interface might be from several types, etc...). So you'll realize that the schema you provided, can be easily transformed to an XML like the one I'm providing, and therefore exported in a common format, regardless of how you do store it. Maybe we just have to adapt some tags/formats or add some attributes to be able to describe all cases. Once all of us do export all the data in a common and understandable format regardless of the technology or application used, will be very much easier to reuse components and logic. Let us know once you have the wiki ;) CNML generated DTD: -------------------------------------------------------------- CNML generated schema: -------------------------------------------------------------- Al 30/11/09 20:46, En/na Mitar ha escrit: > Hi! > > We have prepared documentation for our schema. It is available here: > > http://wlan-lj.net/wiki/Podrobnosti/NodeWatcher/Schema > > I think the important thing is to define globally unique IDs for all > nodes in all systems which would not change during a lifetime of a node. > We are using UUIDs to achieve this. > > In this way it is not just possible to interchange code/modules but also > data about nodes. So there could be someday also aggregating system for > all our systems (for example a global map of all nodes). > > I could fork our schema documentation and it could start as a schema > draft where everybody would start adding your fields and discuss names > of common fields. We can use our wiki for that if you wish. > > I think it would be also useful to invite also other wireless networking > groups to this. Especially overseas ones. What do you think? > > > Mitar > > _______________________________________________ > Nodedb-interop mailing list > Nodedb-interop at lists.funkfeuer.at > http://lists.funkfeuer.at/mailman/listinfo/nodedb-interop > -------------- next part -------------- An HTML attachment was scrubbed... URL: From (spam-protected) Mon Nov 30 23:21:42 2009 From: (spam-protected) (L. Aaron Kaplan) Date: Mon, 30 Nov 2009 23:21:42 +0100 Subject: [Nodedb-interop] changed summary text of our group Message-ID: Changed the intro text to: This is the list which was created at the Rome meeting in order to unify our node databases. The goal now is to find a common "language" of node databases so that we can independently write services for each other and it will work. Also it is very good to learn from each other's node DB . Result should be a wireless community network "RFC" which describes our node DBs. - - - - - - - I hope this is OK for you, I believe some text / description which comes out of our common agreements will be very helpful for other community networks. As soon as we have a first draft (and some *working code* ("rough consensus and working code")), I would like to let the other community wifi networks know. One thing I would like to point us to is the open-mesh.com format: The request is encoded in a HTTP GET string (urlencoded) and the answer is a HTTP "name: value" pair. I can give some samples if needed. very cool that we are working on all of this now :))) horray! From (spam-protected) Mon Nov 30 23:45:56 2009 From: (spam-protected) (L. Aaron Kaplan) Date: Mon, 30 Nov 2009 23:45:56 +0100 Subject: [Nodedb-interop] changed summary text of our group Message-ID: <081D2FE6-4865-4986-A71D-945F57A26438@lo-res.org> Changed the intro text to: This is the list which was created at the Rome meeting in order to unify our node databases. The goal now is to find a common "language" of node databases so that we can independently write services for each other and it will work. Also it is very good to learn from each other's node DB . Result should be a wireless community network "RFC" which describes our node DBs. - - - - - - - I hope this is OK for you, I believe some text / description which comes out of our common agreements will be very helpful for other community networks. As soon as we have a first draft (and some *working code* ("rough consensus and working code")), I would like to let the other community wifi networks know. One thing I would like to point us to is the open-mesh.com format: The request is encoded in a HTTP GET string (urlencoded) and the answer is a HTTP "name: value" pair. I can give some samples if needed. very cool that we are working on all of this now :))) horray!