Konstantin, Thanks for letting us know. Providing input here or if you have a JIRA user (should be self-registering) file tickets there is a good way to start. Those with significant input who are happy to sign the Apache Contributor Agreement could eventually join a PMC and become committers, if they want.
Regards, Werner On Tue, Jan 20, 2015 at 5:26 PM, Konstantin Papkovskiy < [email protected]> wrote: > Hi, Werner > > No, I am not a contributor. But I am very interested in further development > of this project and willing to help. > > > Regards, > > Konstantin > > On Mon, Jan 19, 2015 at 1:50 PM, Werner Keil <[email protected]> > wrote: > > > Konstantin, > > > > Thanks for the input. Are you a contributor already or considering to > > contribute? > > > > What I saw e.g. Unicode stores its vast CLDR data now with JSON as > > preferred format: http://www.unicode.org/Public/cldr/26.0.1/ > > So I guess that looks like a decent future format. > > > > Also badly needed will be a way to convert existing XML into a new > > structure, regardless of the format(s) we end up using. > > > > Werner > > > > > > > > On Sun, Jan 18, 2015 at 2:02 PM, Konstantin Papkovskiy < > > [email protected]> wrote: > > > > > Hi, Reza > > > > > > I have a comment regarding the device data. Some important for us > device > > > attributes are missing in the DeviceMap vocabulary. Specifically, > OpenRTB > > > standard describes the following device attributes that useful in the > > > advertising industry. > > > (see p. 3.2.11 of OpenRTB 2.3): > > > *devicetype* integer The general type of device. Refer to List 5.17. > > > make string Device make (e.g., “Apple”). > > > model string Device model (e.g., “iPhone”). > > > os string Device operating system (e.g., “iOS”). > > > osv string Device operating system version (e.g., “3.1.2”). > > > *hwv* string Hardware version of the device (e.g., “5S” for iPhone 5S). > > > h integer Physical height of the screen in pixels. > > > w integer Physical width of the screen in pixels. > > > *ppi* integer Screen size as pixels per linear inch. > > > *pxratio* float The ratio of physical pixels to device independent > > pixels. > > > js integer Support for JavaScript, where 0 = no, 1 = yes. > > > *flashver* string Version of Flash supported by the browser. > > > > > > I marked bold the attributes that are missing. The full text of the > > > standard can be found here: > > > > > > > > > https://github.com/openrtb/OpenRTB/raw/master/OpenRTB-API-Specification-Version-2-3-FINAL.pdf > > > > > > There is also very relevant note in that document: > > > > > > There are currently no prominent open source lists for device makes, > > > > models, operating > > > > systems, or carriers. Exchanges typically use commercial products or > > > other > > > > proprietary lists for these > > > > attributes. Until suitable open standards are available, exchanges > are > > > > highly encouraged to publish lists > > > > of their device make, model, operating system, and carrier values to > > > > bidders. > > > > > > > > > Regards, > > > > > > Konstantin > > > > > > > > > On Sat, Jan 17, 2015 at 9:28 PM, Reza Naghibi < > > > [email protected]> wrote: > > > > > > > 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 > > > > > > > > > >
