Can someone explain the disparity in the price of standards between the Estonia (EVS) and those procured through other sources? When a standard is written it seems to me that a cost is associated with the development and intiial publication, in other words a copyright. As such all starndards (regardless of source) should reflect similar prices.
Just curious... Rick -----Original Message----- From: Brian Oconnell [mailto:oconne...@tamuracorp.com] Sent: Wednesday, September 24, 2014 12:28 PM To: EMC-PSTC@LISTSERV.IEEE.ORG Subject: Re: [PSES] Buying Standards Please note that I am NOT an advocate of violating copyrights or IP. Most of the (rather complex) PDF spec is in ISO32000-1. Note that PDF malware and non-standard encryption (aka ransomware) is not uncommon; and Adobe itself has a history of security failures. My employer is in the process of removing the Adobe reader from company machines, except where sand-boxed (VMware for Windoze, QEMU for Linux). www.cs.cmu.edu/~./dst/Adobe/Gallery/fileSaveAs.c http://pages.cs.wisc.edu/~ghost/ Brian -----Original Message----- From: ce-test, qualified testing bv - Gert Gremmen [mailto:g.grem...@cetest.nl] Sent: Wednesday, September 24, 2014 6:17 AM To: EMC-PSTC@LISTSERV.IEEE.ORG Subject: Re: [PSES] Buying Standards Well there is Adobe and Fileopen in that chain, as the license basically works with Adobe reader only. Adobe is a well-known "track everything" internet operator. And for those bodies..... they act like commercial companies.... Who looks over their shoulders BTW.....? Gert -----Original Message----- From: John Woodgate [mailto:j...@jmwa.demon.co.uk] Sent: woensdag 24 september 2014 14:57 To: EMC-PSTC@LISTSERV.IEEE.ORG Subject: Re: [PSES] Buying Standards In message <FCA549BE3ECF9D4CB8CB8576837EA48920AA0D@ZEUS.cetest.local>, dated Wed, 24 Sep 2014, "ce-test, qualified testing bv - Gert Gremmen" <g.grem...@cetest.nl> writes: > The single user version is not usable in a commercial environment, as >it "phones home" and might transfer information that is confidential to >my business operations. Do you think a National Standards Body would have anything to do with such malpractice? -- OOO - Own Opinions Only. With best wishes. See www.jmwa.demon.co.uk Quid faciamus nisi sit? 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 <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 <emcp...@radiusnorth.net> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher: <j.bac...@ieee.org> David Heald: <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 <emcp...@radiusnorth.net> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher: <j.bac...@ieee.org> David Heald: <dhe...@gmail.com>
