-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nobody is talking about 2 Ids or any such thing...you either refuse to or just don't get...the rest is 'semantic' gibberish if you can't get fundamentals like that...I despair...and I must wonder
The current Id field is not safe. Persist if you must, but I'm not sure I can continue esjr > +1 > > As mentioned, if automated user-defined entries are added in > future, there could be an algorithm deriving a new ID (ensuring it > doesn't already exist in the DB) but for those entries already > existing we should not overwrite the (usually) human-readable Id > with another one. > > On Mon, Aug 25, 2014 at 9:27 PM, Reza > <[email protected]> wrote: > >> 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 >> >> > 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+5FjAAoJEOxywXcFLKYcGJsH/RyDJorzPToaO5oCCTKZIoSK Es+2rEn6H5yhivJNRv8zHPN2XfqAln+fsbb718b5ikizo2Sa0gf49dQQW22wfKA2 bROmnPzTLhiWsnw9yGawNyIo3kQc5quKP5tX+kS0YzASDkkxYtViCc2WkxqLWoh6 X0zKtEpiKxhnXvhKwhc5poLAS3C7HW2rgbA6re5LcRKIHj/yJkVmWR0TlkYtKMvo UvD506bTKx9xnP8SNLgBiyUzRarvMT4o+BVHU8+Lw69D/y7sqbptAfaklWnfIlv0 /nu//eQ24rgEFtoSbqUEa55tA4M9ybjVsDomsi/K9jJ4oUvG6KjyYW/q3soY1UE= =2KyZ -----END PGP SIGNATURE-----
