In message <[email protected]>, dated Fri, 26 May 2006, Camille Good <[email protected]> writes
>"Why" is as important as "what" when it comes to reading & applying >product safety requirements, but "why" is typically never documented, >except in the memories and private correspondence of those who have >been working in product safety for years or even decades. Going to the >standards meetings, or finding an expert willing to answer questions, >is the best way to find out "why". The climate in IEC has certainly changed in this respect. Now, in many committees, including TC108 and SC77A, it is necessary to publicly explain 'why', either in the standard or in a 'rationale' document, which may be an IEC Report. For an example, see IEC 61000-1-4, although the explanations are incomplete because some of the ancient documents (pre-1991!) were unobtainable. -- OOO - Own Opinions Only. Try www.jmwa.demon.co.uk and www.isce.org.uk 2006 is YMMVI- Your mileage may vary immensely. John Woodgate, J M Woodgate and Associates, Rayleigh, Essex UK - This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. Website: http://www.ieee-pses.org/ To post a message to the list, send your e-mail to [email protected] Instructions: http://listserv.ieee.org/request/user-guide.html List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas [email protected] Mike Cantwell [email protected] For policy questions, send mail to: Jim Bacher: [email protected] David Heald: [email protected] All emc-pstc postings are archived and searchable on the web at: http://www.ieeecommunities.org/emc-pstc
