Shadowrun General > Gear

What's in a SIN?

(1/4) > >>

Irian:
A SIN is, technically spoken, a number (or more accuratly, probably an alphanumeric character string). I like to think about it as an "identification number", like the number on your passport today. It is, of course, used as an id to store data about you into a database. For example, if a shop sells you something, they will insert an entry into the shop's database like "Sold: X and Y to SIN Z.". Or if you get jailed, the government will insert an entry into your criminal record (which itself consists only of entries in a government database) like "SIN X convicted for Y and Z." (simplified, of course).

The big question is: How much information does this number include in itself?

For example, an identification number on a german identity card (21 digits) contains the birth date, the expiry date, nationality, authority code and some error checking numbers.

So in Shadowrun one could argue, that an ID that is primarily transmitted electronically could be much longer and thus contain much more data in itself. For example, the SIN could contain a hash of the retina (a, let's say, 32 digit number that can be computed from the data gained by scanning your retina - and stays the same every time you scan - and theoretically, it should be impossible to calculate what the retina looks like when only having the hash).

Is there information about what IS stored in a SIN itself? What can you check with a given ID if you don't have access to any government, etc. database?

The_Gun_Nut:
As I understand it, the SIN contains all that information and more.  It has birthplace as well as the date, and enough information to positively identify someone based upon fingerprints, retina patterns, and DNA patterns.

It also appears to be an evolving ID, meaning that based upon the subjects purchases, movments and financial and personal records, keeps up with the major changes and trends within the persons life.  Highly complex, as I understand it.

Irian:
I understand that it could contain such data as DNA (hashed, as described), etc. but I do not understand how the number should be able to CHANGE. It's an identifier, how should it change? That's like saying "Hello, my name is Frank 148$ in my bankaccount Miler. Ups, no, it's Frank 142$ in my bankaccount Miller. Oh, no, it's Frank 142$ in my bankaccount with green trousers Miller. Erm... Wrong again... It's now..." An ID has to stay as it is, that's the important thing for an id. If the ID would change, how would you prevent that someone simply introduces himself with an older one? If you have to cross-check it, if it's the most recent one, the whole process of storing information in it is worthless, as you could have simply asked a server from the start :-)

The_Gun_Nut:
The first part of the number, birthdate, birthplace and basic identification, can remain the same while the secondary part can be added onto and evolve over time.

Irian:
And again: What for? It's a good idea to include some biometic data to be able (offline, without having to connect to some other computer) to say "Yes, the man IS the owner of SIN XYZ.". But abusing the SIN to double as a database itself doesn't make sense, sorry.

Navigation

[0] Message Index

[#] Next page