Do you have any feedback for 2.0 [0]? So we are doing a few things: -partitioning detection into device, browser, and os. No explanation here, should be clear why this is needed.
-creating a specification for data and apis to interact [1]. Similar to the above partitioning, this will allow for data and code to evolve independent of each other. This is already happening with the potential introduction of new classifier clients, like your ruby client...! 2.0 is still in its very early stages, so feedback is important. The reference client will be a clear guide to 2.0 implementation. This will be coming in the near future. [0] http://wiki.apache.org/devicemap/DeviceData2 [1] http://wiki.apache.org/devicemap/DataSpec2 <div>-------- Original message --------</div><div>From: Konstantin Papkovskiy <[email protected]> </div><div>Date:01/17/2015 4:14 PM (GMT+01:00) </div><div>To: [email protected] </div><div>Cc: </div><div>Subject: Re: Mobile to be Next UX Battleground </div><div> </div>Hello all DeviceMap has also great potential in the advertising industry. It helps to improve advertisement targeting. For example, I am working on real-time bidding advertising marketplace (OpenRTB exchange) and the project like DM is required in order to implement it. See http://openrtb.github.io/OpenRTB/ if you are interested. This is one of the reasons why I started to implement the ruby classifier. Regards, Konstantin On Sat, Jan 17, 2015 at 5:16 PM, Werner Keil <[email protected]> wrote: > Hi, > > Guess that is a good reason why a project like DeviceMap will be even more > important in the future: > > http://www.information-management.com/news/Mobile-Customer-Experience-User-Experience-Gartner-10026421-1.html?utm_campaign=daily-jan%2017%202015&utm_medium=email&utm_source=newsletter&ET=informationmgmt%3Ae3668581%3A1927094a%3A&st=email > > Werner
