I also agree in large part with Ted and Rich. There are periods during the development cycle where stakeholder input is sought. This is a time, usually at the end of the CD and DIS stages, where the National Committees are expected to consult with their stakeholder groups, and then assess and compile the results of those reviews for submission as part of the voting process.
There can be significant differences between the CD or DIS versions of a standard and the FDIS version due to these comments, but once a standard reaches FDIS, there is little opportunity for change until the next edition is published as only editorial changes and not technical charges are allowed at FDIS. The best way to know about what is coming is to be part of the process. Doug Nix d...@ieee.org +1 (519) 729-5704 > On 19-Mar-18, at 13:27, Richard Nute <ri...@ieee.org> wrote: > > > I largely agree with Ted’s observations. > > “Most often, we need the submitter to provide more details at the meeting > before the committee can make an informed decision about the proposed change.” > > The IEC/USTAG comment forms have limited space for comments. One MUST attend > the meeting to adequately present and defend the comment. The committee > simply won’t take the time to understand the comment in the absence of the > author. I speak from experience as a corresponding observer of the USA > National Committee. > > Rich > > > - > ---------------------------------------------------------------- > 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 > <emc-p...@ieee.org <mailto:emc-p...@ieee.org>> > > All emc-pstc postings are archived and searchable on the web at: > http://www.ieee-pses.org/emc-pstc.html > <http://www.ieee-pses.org/emc-pstc.html> > Attachments are not permitted but the IEEE PSES Online Communities site at > http://product-compliance.oc.ieee.org/ > <http://product-compliance.oc.ieee.org/> can be used for graphics (in > well-used formats), large files, etc. > > Website: http://www.ieee-pses.org/ <http://www.ieee-pses.org/> > Instructions: http://www.ieee-pses.org/list.html (including how to > unsubscribe) <http://www.ieee-pses.org/list.html> > List rules: http://www.ieee-pses.org/listrules.html > <http://www.ieee-pses.org/listrules.html> > For help, send mail to the list administrators: > Scott Douglas <sdoug...@ieee.org <mailto:sdoug...@ieee.org>> > Mike Cantwell <mcantw...@ieee.org <mailto:mcantw...@ieee.org>> > > For policy questions, send mail to: > Jim Bacher <j.bac...@ieee.org <mailto:j.bac...@ieee.org>> > David Heald <dhe...@gmail.com <mailto:dhe...@gmail.com>> > - ---------------------------------------------------------------- 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 <emc-p...@ieee.org> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe) List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <sdoug...@ieee.org> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher: <j.bac...@ieee.org> David Heald: <dhe...@gmail.com>
