User Tools

Site Tools


datasets:naming

Naming of data sets

Introduction

When publishing data sets from different sources, it is important to agree on a common naming scheme. Otherwise, comparison is impossible. At the moment, a number of existing proposals to name CN components exist:

Funkfeuer proposal

(Inserted by Bart) This is the current proposal of Funkfeuer to name entities in datasets, as documented on Github:

Node

By node we denote a physical location where one or multiple devices are grouped together and are directly interconnected on layer 2.
A node is not to be confused with a device. 

NodeDB

Strictly speaking, the nodeDB is the set of different registries (IP address, nodes and device registry and person registry). There are other components (as mentioned in the introduction) which interplay with the nodeDB. For example the map, the dashboard, etc. These components usually query the nodeDB via a REST interface.

Device

By device we mean an individual piece of  (router) hardware which is an independent participant in the mesh network.

Dashboard

By dashboard we denote the main user interface through which a user of the community wireless network can see "his" community wireless network. It also gives the user a comparison actual data of the network (statistics, reachability etc) with the stored data in the nodeDB

Guifi proposal

Guifi also has a method to name components in their CNML data, a short overview is given on their wiki:

<cnml> <hardware capabilty> <siftware services> <devices> cpu, memory, storage, devices, radio level etc. </devices> <mapping> gps, name </mapping> <statistics></statistics> <network environment> <content sharing> <node information> <owner of device> <picopeer> <traffic> <scale of interest to the network> <personal keyring>(hold private, only given volountary) </cnml>

A more correct format is described in the CNML overview.

datasets/naming.txt · Last modified: 2013/01/09 14:03 by braem