As for your other question, would device map be more active if it had device data?
Yes, I believe so. First, I've pointed this out several times, the current implementation is not entirely accurate. This is due to the ODDR legacy. I rewrote the api which address many aspects of it, but the next step is to take control of the data so the 2 parts (data and api) are married in a more complete way. Right now they are disjointed, patterns are added without any knowledge of how they are best matched by the pattern matcher in the api. Also, the data gets copied over from ODDR. Its unknown whether ODDR is still active. The website is down. This risks the entire device map project. Also, the data in itself is very useful. It doesnt need to be used with the api. I for one would port my dclass project to the data, so you will at least have 1 other project using this data. Im sure other projects would want to leverage this device data as well. Devices are the future, so there should be a project which captures and classifies these devices in a meaningful way. ________________________________ From: Bertrand Delacretaz <[email protected]> To: "[email protected]" <[email protected]> Cc: Reza <[email protected]> Sent: Friday, June 27, 2014 11:27 AM Subject: Re: DeviceMap Community - Incubator PMC/Board report Hi, On Fri, Jun 27, 2014 at 4:56 PM, Werner Keil <[email protected]> wrote: > ...there has never been the vitality we'd hope if there was finally an > infrastructure here... IIUC you mean that DeviceMap would be much more active if people could easily submit device data. If that's correct, how do you see this? What's the simplest setup that allows that to happen? -Bertrand
