Well, it would be 1 of 2 ways: 1) a developer or contributor keeps the data up to date privately. This is similar to how openddr is working today. The problem with this approach is that it can easily fail if said developer does follow thru. Also, said developer has to have great visibility into the device space to be able to stay on top of new devices that enter the market.
2) create a website which allows user agents to be tested and new devices to be submitted. So the scenario is that we release the device data and api and a user finds a new device which does work. They goto the website and enter in the user-agent and the website confirms the device does not match or the match is invalid. The user then submits the user-agent into a queue where a developer then looks at the user-agent and adds a new pattern (or fixes an existing pattern) to make the device match properly. If its a new device, the device attributes are added in as well. This new pattern and device are picked up in the next release. Is this what you were asking for? ________________________________ 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
