For *harmonized* standards, did an add-on utility last year that is both a diff and grep to discern this stuff. Dates, scopes, and links to the electronic file are part of the tables. Used the Python difflib and grin with CSV files. Sorting is whatever you wanna do, and limited only by what and how one is willing to populate the tables.
ANSI, ASME, Mil, etc also have ISBNs, but are structured differently so comparisons may require a smart parser if you wanna do anything special with database queries. Should also note that UL, for a cost, offers red-lined versions of standards. Meanwhile, back at my more typical and mundane life of writing test reports... Brian -----Original Message----- From: Doug Powell [mailto:[email protected]] Sent: Saturday, June 24, 2017 3:54 PM To: EMC-PSTC; Brian O'Connell Subject: Re: [PSES] Organize my standards => ISBN 13 Digit code Interesting idea to use ISBN. It would be a unique identifier. I am curious to know what everyone feels is the best practice for sorting a database on harmonized standards. For example, all of the 61010-1 national derivatives and national differences for IEC, EN, ANSI, CSA, UL, etc. I have in a spreadsheet a separate publisher column and the base document number. I also track publication date and date of withdrawal, if available. I am a bit of a pack rat in this regard, I keep most of my data forever plus or minus a few decades. Sometimes when I have an updated publication available, I do a textual word by word comparison document to flag the differences. I am frequently surprised and the number of "editorial" changes that do not make it into the change logs or the magazine articles or even the big four certifying agencies here in the USA. Doug Original Message From: [email protected] Sent: June 23, 2017 6:18 PM To: [email protected] Reply-to: [email protected] Subject: Re: [PSES] Organize my standards => ISBN 13 Digit code When you have bazillions of standards, the ISBN is handy as a unique identifier (unique and/or primary key), as each version has different reference; otherwise no other significant use. For example, an excerpt from my database: ISBN 9780580910234 BS EN 62368-1:2014 ISBN 9782832214053 IEC 62368-1 Edition 2.0 2014-02 ISBN 9782889106844 IEC 62368-1 Edition 1.0 2010-01 ISBN 97811554364159 CSA C22.2 NO. 60950-1B-07 Brian From: Chuck August-McDowell [mailto:[email protected]] Sent: Friday, June 23, 2017 4:47 PM To: [email protected] Subject: [PSES] Organize my standards => ISBN 13 Digit code Greetings form Berkeley, Does using the International Standard Book Number (ISBN) 13 digit code work to organize your standard's collection? Thank you in advance for comments, Mr. Chuck McDowell Compliance Specialist Meyer Sound Laboratories Inc. - ---------------------------------------------------------------- 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.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 <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
