3 ms·
Instead of "enforcement" I would appreciate good "standards". This allows for improvement and reasonable exceptions. I would provide a "customer traffic light"
by ho_schi 4y ago
Instead of "enforcement" I would appreciate good "standards". This allows for improvement and reasonable exceptions. I would provide a "customer traffic light" informing about specific features.
More specifically I would shift from implementation (How?) to actual requirements (What?). The implementation is a decision of the manufacturer. Examples:
* User-replaceable batteries # By Screw? Coin? Flip/Notch on outside? Behind Backcover? Whatever.
* Hardware-maintenance-manuals # Explosion Diagrams? Text? Step-by-Step? Whatever.
* Locally user replaceable firm- and software! # By Thumbdrive? SD-Card? USB-Cable? Whatever.
Historic example. Do we want enforce a specific engine type {turbojet, turbofan, turboprop) on planes or a specific noise level? The later! Similar for the EU-Cookie-Directive. They should have stated that tracking of users is forbidden (What) and not how to handle Cookies (How).
- hcal 4y agoI'm probably overlooking an obvious answer, I'm not sure how you define this clearly. Using your noise level example, we know how to measure noise levels. It is straight forward to say your new technology complies with a noise regulation. How do you do that for a regulation like standardized connectors? Just say you can't use any non-open-standard connectors?