Hegart ...

Having done a bit of research on this topic over several years, my own 
plans are design systems for the use of PlaceOfBirth and TimeOfBirth as a 
composite unique key.  There are deep historical reasons ( e.g. Inheritance 
by first born ) that result in even identical twins who are born at the 
same time, being "timestamped" one minute apart.  Furthermore, GPS 
resolution at 18" is now good enough that adjacent beds in the same 
maternity ward can be uniquely resolved. Moving forward, it will be 
increasingly rare for someone to not know their precise ToB.PoB.  Then, 
given the ease with which "official" documents can be joined to such a key, 
it will be possible to construct further unique keys that are applicable to 
each and every particular context.

Interestingly, TiddlyWiki's superb Tag support makes it possible to hash 
such keys using a character set (alphabet) of the more than 100,000 
characters defined in the Universal Character Set or the 2*31 codepoints 
that are currently allowed for.  In effect, it is possible to come up with 
a unique hashTag for each and every person in as little as 2 characters. 

As for UUIDs, I'm rather leaning towards the use of the cell phone SIM ID 
and the MAC ID as keys that will access any and all phones.  This is baed 
on the assumption that everyone will inevitably have one ( even if they are 
not "implanted" immediately at birth ).

My apologies if this sounds extreme, but it's such a long-standing interest 
for me, that I often find myself talking about it to the point of boring 
others.

Cheers,
Hans


On Sunday, April 17, 2016 at 6:20:41 PM UTC-4, Hegart Dmishiv wrote:
>
> Hi Hans,
>
> Interesting discussion point. I can't say I've ever seen, nor even 
> considered, a situation where Name + GeoLat + GeoLon = Identity. I have 
> thought of adding geolocation to TiddlyCRM, naturally, as it is a common 
> feature in other, big-name CRMs, but I wouldn't conceive of it becoming 
> part of the "primary key" for an individual. We've been debating about 
> primary keys lately within the TiddlyCRM team, with the possibility of 
> using a UUID instead of Surname + Firstname, but we've settled for now on 
> the latter. We may still change to UUIDs in the future though.
>
> Hegart.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/613458c9-ba23-4422-869a-73993a72ea5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to