Quote:
Originally Posted by Phaneuf3
so? the thing fails because of malfunction or where you are and.... you're stuck using the methods we have now... its not like you're any worse off for having the chip.
|
Sure, if you are willing to ignore all the other concerns already raised.
Quote:
Originally Posted by Phaneuf3
but there's also a TON that everyone will (relatively) happily agree on... http, ftp, tcp/ip, dns, etc, etc.
and even if there are two standards for europe and NA, building a reader that could handle both wouldn't be the end of the world. an example of something like this would be cell phones that are compatible with both standards or the switchover from IPv4 to IPv6. or simply relying on it for 99.99% of the chips that you'll see in your area and the rest you'll have have to deal with the old fashioned way...
rejecting this idea on the basis that sometimes the system might fail and we'll be forced to do what we do right now is a pretty bad way to go about assesing the situation IMO.
|
Those standards were (generally)developed by one group who maintains control over the entire structure. Even then, you get issues with page rendering (IE6/FF/IE7/Opera, and so on) issues with proprietary plug-ins (quick/real/shockwave/flash/Active-x), ASP/PHP, and so on. And in a roll-out like this there will be hundreds of companies wanting to be a player.
It will NEVER be universal.
That is why a number that related to a database entry of your stuff will probably never work. It will be totally impractical. You think the gun registry was a boon-doggle? Try implementing something like this system.