In message <[email protected]>, dated Thu, 9 
Jul 2009, Brian O'Connell <[email protected]> writes:

>With no intent to be flippant, nor disrespectful.
>
>Why ? To what end ?

You made an unqualified statement:

1. IEC/EN60065 is not adequate for the discussed scope

You go on to say:

A product safety standard is not sacred. A product safety standard is 
not immutable. A product safety standard is the best reference resource 
to get the job started.

But what is important, at least for the good people of the PSTC, is to 
discuss what could be good and what could be bad. And we have just done 
that.

It seems clear to me that you think you have found a weakness in IEC 
60065, leading to your first statement.

Considering the second and third statements, with which I agree, it is 
surely appropriate that your finding should be sent to the people who 
can consider its merits and, if justified, eliminate the weakness.

In submitting your findings, there is certainly no requirement, and no 
need, to participate in the actual committee work. If you choose not to 
submit your findings, that is inconsistent with your second and third 
statements.
-- 
OOO - Own Opinions Only. Try www.jmwa.demon.co.uk and www.isce.org.uk
Things can always get better. But that's not the only option.
John Woodgate, J M Woodgate and Associates, Rayleigh, Essex UK

-

This message is from the IEEE Product Safety Engineering Society emc-pstc
discussion list. To post a message to the list, send your e-mail to
<[email protected]>

All emc-pstc postings are archived and searchable on the web at:
http://www.ieeecommunities.org/emc-pstc
Graphics (in well-used formats), large files, etc. can be posted to that URL.

Website:  http://www.ieee-pses.org/
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]>

Reply via email to