Not sure, if the 4k or so UA strings for just a SINGLE device as mentioned are all unique, but if those were stored in an RDBMS or similar DB, then a unique constraint between UA string and an attribute like device name/id would do to filter out identical duplicates.
In such cases, not the XML device information a generic ID (either just a number or something like UUID) may work, but that's up to a DB whatever works there? On Tue, Aug 26, 2014 at 11:42 PM, eberhard speer jr. <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > most interesting [aside from 2.0 becoming Data 1.0.1, but I'm sure > Werner knows why]...that brings me to another question that's been > 'bugging' me : > > How do we propose to keep and maintain the device data, manage it and > manage 'publications' ? > > esjr > > btw : not to kick a sore point but exactly how do we know "new" is new ? > > PS : bots came back : harvested +4K uaprofiles [most will proove > duplicates after testing] and logs are in too : +250k 'new' [sort of] > UA-strings...you know, the RDBMS thing, structure and all that boring > jazz... > > > > As seen on below list, there is no "unique" UA string it seems but > > see > > http://developer.nokia.com/devices/device-specifications/nokia-lumia-635 > > > > > (Expand All) > > this Nokia Developer reference quotes a (hopefully representative) > > example UA: "Mozilla/5.0 (Windows Phone 8.1; ARM; Trident/7.0; > > Touch; rv:11.0; IEMobile/11.0; NOKIA; Lumia 635) like Gecko" > > > > P.s.: As asked by an attendee of a recent conference, the chip > > architecture (like ARM) seems to be part of some UA strings now, > > too. > > > Werner > > > > > Must be harvested via an automated sytem, it is hard to believe > > manual entry copes with Hundred Thousands unique UA strings... > > > > This site has some sort of UUID (for the myriads of strings) but > > unlike the actual UA string ("Nokia100/2.0 (2.0423.0_rc02) > > SymbianOS/7.0s Series60/2.1 Profile/MIDP-2.0 > > Configuration/CLDC-1.0" for Nokia 100) it should be assumed unique > > to the site and must not be used. > > > > have 18 devices ready for 1.0.1. Still need user-agents for 16 of > > them :) I think ... Here are the devices: > > > > > https://issues.apache.org/jira/browse/DMAP-67?jql=project%20%3D%20DMAP%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Device%20data%22%20AND%20status%20%3D%20%22In%20Progress%22%20ORDER%20BY%20priority%20DESC > > > > > > Also, when I search google for: > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > > iQEcBAEBAgAGBQJT/P9EAAoJEOxywXcFLKYcE+QIALu3nAhfHDtzMkV8qYZ+YwSU > lV0glq2H5ItkfoSwntXRYiE8hhm/GAtNg0SlQY7CEUzw7ZVb5/Ro4YlEYmMMH1hc > MjocWnBMVwqwVKyPk/EFV+zWC2kbcb3EAzPuS3VabbHlFc6/3qENHosN6JgxRA1+ > dSaINOIVSr+EjKKtYj6pb/JlsZ72zzOlsT9LESPnPH8MqqOlGMCdMFrCwL6kvbX7 > 2RqI6k8aajSiuJ+OJnQGAeix5lz8SW/wkMM2ruxF+VNp+vyI8AeDLsrC0yizunkV > Ojm4Z5VeCAmYrYkgY6Fecaj8dJiUSOZVcl2ZJu7F+RSEJ7Oomu/GSTxw+Q0G4i4= > =jYlK > -----END PGP SIGNATURE----- >
