Hacker News new | ask | show | jobs
by coldtea 1089 days ago
Perhaps part of a product, each supplier, and each changed spec should contribute to a unique fingeprint.

If you have a product which you keep calling FOO but has changed some spec in the new version (without hw change, perhaps you enabled some firmware option and now it can record 25 minutes instead of 20), it should get a new fingerprint. If it has changed a supplier for a chip, new fingerprint. And so on.

And aside from the fingerprint, you should also give all the entries that contributed to it (which when hashed in a structured function should give the same fingerprint), plus things like its production date.

Name="FOO", cpu.model="x-dragon-v5", cpu.supplier="Fukimata Japan", ..., fan.supplier="Fans-R-Us",...

Reviews then are tied to the product+fingerprint instead of just the product.

1 comments

I work in data management for large companies and I can promise you the problem is not a technical one. Which organization has the maturity to actually follow-through with quality data for such systems? Which legislators have the power to enforce such an approach?