On Sun, 1 Jun 1997, William H. Geiger III wrote:
In <Pine.SUN.3.95.970602014607.25651C-100000@netcom2>, on 06/02/97 at 02:24 AM, jonathon <grafolog@netcom.com> said:
Really much to complex to be of use not to mention the lack of reliable data to form the id #.
For person's currently living, maybe the data is lacking. However, tagging an ID at birth, for future citizen units, is perfectly feasable. << And do note in passing that hospitals do have SSNs issued to new-borns, regardless of the wishes/request/knowledge/authorization/permission of parent(s). >>
The use of DOB + Geographic Identifier + Unique Code would work quite
Err, the code I listed was of that format --- just a lot more more specific than the following.
19970601 - DOB. 0123 - Sample Geographic Identifier (say NY City). 0142 - Unique Code added to handle collisions of the above two.
I believe that this is very simmilar to what the SSA uses though I believe that they only encode the year of birth when calculating SS #'s.
SSN consists of xxx-yy-zzzz xxx is state of issue. yy _can_ correspond to year(s) of issue, and locale with the state. << Usually just a range of years that it was issued in. >> zzzz is the sequence number. Each issued number just goes up one more. Though certain numbers are deliberatly skipped. There are certain checks that can be done, to figure out if a number _could_ have been issued to an individual.
of digits required. I would imagine that the SSA will have to go to a Hex or complete Alphanumeric codings system as the population increases.
They currently recycle old numbers, though there are still a number of unused sequences that are available. << Roughly the current population of the usa. >> xan jonathon grafolog@netcom.com Monolingualism is a curable disease