So I think you are talking about a GUID here... So is a GUID an attribute of a device? So a device has screen dimensions, CPU and hardware specs, pixels, a manufacture, etc. These are device attributes.
Is a GUID a device attribute... No. A GUID is DDR metadata. We already have a metadata ID field, its called 'id'. Its human readable, it links devices with their patterns and it works pretty well. If you want to add a second metadata ID value, where do you store it? In the device attributes? In the browser attributes? In the OS attributes? Do devices, browsers, and operating systems need GUIDs and regular IDs? Or are we only assigning GUIDs to devices? When do we use the ID and when do we use the GUID? When (and why) would a client actually use a GUID instead of the ID? How and who generates the GUID? I think its best to just have 1 ID. The last thing I want is for people to start associating devices, browser, and operating systems by these GUIDs. IDs work fine here. ________________________________ From: eberhard speer jr. <[email protected]> To: "'[email protected]'" <[email protected]> Sent: Monday, August 25, 2014 3:14 PM Subject: Re: Data 2.0 - Vocabulary Properties : ddr_ and guid -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So, no one sees the sanity of having an identifier that 'travels' well [think http, think XML, think json...encoding] besides a human-readable pseudo-identifier [common practice] ? Despite the fact that the DeviceMap [OpenDDR] data itself already clearly shows signs of having bitten by that 'bug' [barnes & noble vs. barnes and noble] in *non*-key data... I am baffled. esjr -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJT+4skAAoJEOxywXcFLKYc3ykH/0oXmlmrvh0nTGUgjUH8R9nh UHGVsuHDiU0DG2J9aoFW0a3WvJUKfeQWuKO4zaHzkegD1fbtBgOTYTX//kNa74RJ yMhyU2yc75ZnPUjUd7t3/wZwW1as74wTgDftOA72j+EyXR1dyZwssEw1K4kRnXI8 F/QJqe4QaR7dxvp5x2SpkuDJ4R9Ypohz5dNcNuI4ImkGtBQYlIe0K0JIMbBvpWq4 7dxYs+dBzM5F2ZM4hA2oGTGTg+/JsNP0vB8TWd5gxTwFzvz7kE3jip49qiRRVJlw ZSYW6KqmXEiqMNgmWkHvxo0BZceknwNZjrKtgdIOAoea0/2LJ4+eKcKPZn9vM7g= =muRs -----END PGP SIGNATURE-----
