Slashdot Mirror
An ID Number for Everything
jon323456 writes "Put this in your privacy pipe and smoke it. According to news.com, MIT researchers have cooked up a new barcode that has enough dataspace to include a unique serial number for everything. And in combination with RFID tags...."
Gillette was listed as an attendee. This is the same gillette who took photos of customers purchasing their products using an rfid-triggered cameras.
It has been shown that IPv6 will provide 4 IP numbers per square centimetre of space on earth. That should be enough to cover all products. My proposal would be to make the UPC the same as a IPv6 number, and then make the barcode show the item's IPv6 address. Network configuration would be simplified - just scan the barcode - and the item wouldn't need a UPC *and* a IPv6. They would be the same. That would simplify marketing and tracking as well, items such as coke cans and underwar could simply be ping:ed on the net. No need to bother with those RFID tags.
"Under EPC, every can of Coke would have a one-of-a-kind identifier."
It occured to me that it's quite possible that such unique id's on consumable items could later get tracked back to their purchasers, then automatically impose a littering fine on them if said Coke can is found empty and discarded on the ground somewhere.
I don't really see that as becoming a reality, but it's possible.
Trolls lurk everywhere. Mod them down.
To be usable, the new system would have to mimic the current one, with some bits dedicated to a manufacturer ID number, and some bits for a product-id-within-that-manufacturer numbers, with the new system adding more bits for individual-item-id-within-product number. Each field must be made large enough to accomidate all manufacturers (ie, CocaCola has few products, but ships millions of each, while a book publisher would have thousands of products but with some only shipping a few hundred). This means that a lot of bits are "wasted" -- although they would be available to the manufacturer for their own subdivision. (Let's say it give 32bits for individual item id. A vender could say 1 bit indicated continient it made one, 3 bit for the country, 3 bits for the factory within that country; 7 bit, year; 4 bits, month; 5 bits, DOM; 9 bits, items made that day.)
Sure, for a while. Back in the 70's, I'm sure they figured that 12-bit barcodes were plenty. According to the article, they're now starting to run out.
It's called thinking ahead: Design a system that will last at least twice as long as you think you'll need. Yeah, 64 bits is incredibly huge. They're talking about serializing every product made by every company with a unique id. So say we plan on it lasting 100 years. That's still like 184,400,000,000,000,000 unique id numbers, per year (64bit). Actually, that does seem pretty damn excessive.
But who knows - maybe there will be other uses for this space as well. Using a few bits to encode sizing/weight information, color, hazards, if it's flamable, disposal instructions, etc, to allow simpler devices to read it without having to link to a database somewhere. A good example of this is the licence scanners some bars use: they swipe your drivers licence, and it shows the info encoded on the card, and they compare it against the info printed on the card. It doesn't link back to a database to verify anything, its just a simple device to help prevent fake id's. Same sort of thing could apply here for shipping purposes, and probably lots of other things, too.
It's a lot easier to just use 96 bits now, than switching to 64 now, and then having to switch to 96 again in a few (or many) years.
Speak before you think