Right. I was going thru the data and the more I think about it, the more of a mess it is. I totally agree with Eberhard that the data just isnt right. Each device is assigned all sorts of device/browser/os properties which may or may not be true.
Stuff like is_tablet is not an attribute, its a marketing name. Ie: a touch device with a certain screen dimension that isnt a phone. While this attribute has some meaning today, its likely to be left in the dust a few years from now. What we really need is the pixel size and the measured size (or pixel density). Just my thoughts. So like I said in a previous email, lets stay the course for our 1.1 release and 1.X series. When we are ready to work on 2.0, we need to seriously overhaul this data. ________________________________ From: Werner Keil <[email protected]> To: "[email protected]" <[email protected]>; Reza <[email protected]> Sent: Monday, August 4, 2014 8:08 PM Subject: Re: Tracking new phones for DeviceMap data That's a good question. The "is_tablet" wasn't new, but came exactly from the OMA-inspired group of "underscore" values you sure find in the "hidden" WURFL now, too Old OMA or J2ME era properties contain rseemingly ridiculous boolean flags like times_square_mode_support So while the "is_tablet" must be maintained for some of these "open_db"/OMA ones, it is a good question, what makes a "mobile" and what a "tablet". Formats in between could be simply defined by size of the screen, but there are further core vocabulary properties the current device data maintains like <property name="inputDevices" value="stylus"/> I am not sure, how up to date we are on a Galaxy Note, but unlike older devices like Palm, etc. it may be both, or a combination of "stylus" and "touchscreen". The value is an "enumeration", and the plural form suggests you can have both. However, there are far more interesting factors from smart watch (if there is a web API or browser that counts) to automotive, where the definition of both "phone" or "tablet" may end, though in theory you could see it as a "car-mounted" tablet or phablet. InputDevice for many of these often adds "voice" to "touchScreen". While this is only an extra via Siri & Co. in the car it often becomes the primary one. On Tue, Aug 5, 2014 at 1:26 AM, Reza <[email protected]> wrote: No, phablet is not vocab we should leverage in this case. I think this comes down to what our definition of a tablet is. Are phones with large screen tablets...? > > > >________________________________ > From: Werner Keil <[email protected]> >To: "[email protected]" <[email protected]> >Sent: Monday, August 4, 2014 7:18 PM > >Subject: Re: Tracking new phones for DeviceMap data > > > > >Also something to take into consideration: >http://www.businessinsider.com/there-will-be-four-times-more-phablets-sold-than-tablets-in-2018-2014-7?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+typepad%2Falleyinsider%2Fsilicon_alley_insider+%28Silicon+Alley+Insider%29 > > >especially regarding the pace of adding device data or even something like >"is_phablet" (or does a combination of "is_mobile" and "is_tablet" sound >better?) > > >Werner > > > > >On Mon, Aug 4, 2014 at 11:45 PM, eberhard speer jr. <[email protected]> wrote: > >-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >>Hi, >> >> >>> Could they somehow be converted into a W3C DDR (or whatever we >>> might turn to later) form to amend "live data", too? >> >>Sure, I will start putting together all the existing components and >>resurrect the CRUD UIs. Data download, up-load etc. >> >>I'll have something useful to show by the end of the week, it's mainly >>a matter of putting it together again. >> >> >>esjr >> >>-----BEGIN PGP SIGNATURE----- >>Version: GnuPG v2.0.22 (MingW32) >>Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >> >>iQEcBAEBAgAGBQJT3/79AAoJEOxywXcFLKYclDsH/js6QlYKJJJ2V5QXb9G18DtV >>6y37b4AiSBShG7D4SVI7TAAj9+lmCG7RFE6oKm67DG8zl1X4mdtB7knO52bZuFVE >>/Z/N+hQIZL2v/X1sYyKQlFDZiDWOR4gt06DZ4hjMjSBQo7pKLOROV2BszbmoXvPK >>ChtCVpMkLk3+x3xu1aPtwccMNtS3mqlO2Aq2pkyG7TlYCanmnjwbmWhgDXmUkIU/ >>k3i10v4SKA81KR1vC9nzshLmIWpubUCuBez+O8gLpCAivmxA6X/l7CyLzz1TWz4h >>1zo4BlVvOilfjfZUcwXLnt6o5ElKg+IJkryp9ZiIE3mEyKu4GrSV0Dsa//vhqjI= >>=yBAo >>-----END PGP SIGNATURE----- >>
