Brian et al,
Yes, I have struggled thru several document format changes and now keep
all important docs in both their native format (eg docx today) as well as PDF.
Not an absolute guarantee of compatibility but now there are a couple of
starting points to work to recover documents. Oh yes, I also have a scanner
that will try to inhale and convert any paper to a coherent format.
BTW, I really enjoy the path's that these threads take - they have a
life of their own.
:>) br, Pete
Peter E Perkins, PE
Principal Product Safety & Regulatory Affairs Consultant
PO Box 23427
Tigard, ORe 97281-3427
503/452-1201
[email protected]
-----Original Message-----
From: Brian O'Connell [mailto:[email protected]]
Sent: Tuesday, September 19, 2017 2:00 PM
To: [email protected]
Subject: Re: [PSES] power strip details -> electronic document preservation
Believe that preservation of legacy electronic documents is very important, and
am happy to see someone attempting to preserve this stuff.
Please note that 'doc' and 'docx' are not usable standards (even where the
OOXML is supposedly per the ISO29500 format) and is ill-suited for reliable
backups and long-term archives. The originator of the standard chose to break
the their promise of backward compatibility with ECMA376, so there is reason to
distrust compatibility of files with future versions of whatever the document
standard de jour would be. OOXML documents, even when displayed on similar
platforms, are oft rendered differently.
Other more reliable and less volatile document standards should be
investigated; for example ISO26300. The ISO and IEC do not seem to understand
the significant risks of data loss where poor document standards are being used.
Brian
-----Original Message-----
From: mickm [mailto:[email protected]]
Sent: Tuesday, September 19, 2017 1:08 PM
To: [email protected]
Subject: [PSES] power strip details
Ralph,
The IEEE is a not-for-profit organisation, but if there is a chance of
making money they will do so. Traditionally you can still buy withdrawn
standards.
Having revised several old C62 standards the biggest problem I found is
that the IEEE loses the source text or graphics or both in the passing years
since the document was created. From these experiences I then under took a
mission to grab what C62 materials the IEEE still had available and convert
them into a Microsoft Word format. C62.41.1 was one document I rescued in 2008.
Thus the Surge Protective Devices Committee (SPDC) does a Word document
available that can be revised and it would be published as something like
C62.4.1.1 2019.
To your last question what does MSPD stand for, it's Multi-service Surge
Protective Device, a device that internally houses a collection of power SPDs
and signal SPDs all with a shared ground reference bond.
IEEE Std. C62.50-2012
multiservice (multiport) surge protective device (MSPD): A surge protective
device providing protection of equipment connected to two or more services such
as power, telecommunications, signaling, data, etc., with the respective
conductors routed via a common enclosure in which an internal shared ground
reference bond has been provided among these services during surge conditions.
Regards,
Mick Maytum
Safety and Telecom
Standards
[email protected]
-
----------------------------------------------------------------
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]>
-
----------------------------------------------------------------
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]>
