Dwight, in my experience, folks in the IT community simply do not use the same vocabulary as folks in the archives community. So, unless they have specifically addressed the kinds of issues embodied in the OAIS Reference Model I cited before, and other work in the areas specific to long-term preservation of electronic records, it doesn't mean anything for preserving very long-term and permanent records.
I haven't looked at DoD 5015.2 v. 3, but I assume the interop issues to which you refer are some of those addressed by ISO 10303 "Automation systems and integration - Product data representation and exchange" [AKA "STandard for the Exchange of Product model data (STEP)"]. DoD was (and, I believe, still is) actively represented on ISO TC 184, Automation systems and integration, sub-committee SC 4, Industrial data, which developed ISO 10303.
The description on Wikipedia of ISO 10303 is "The International standard's objective is to provide a mechanism that is capable of describing product data throughout the life cycle of a product, independent from any particular system. The nature of this description makes it suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases and archiving. Typically STEP can be used to exchange data between CAD, Computer-aided manufacturing, Computer-aided engineering, Product Data Management/EDM and other CAx systems. STEP is addressing product data from mechanical and electrical design, Geometric dimensioning and tolerancing, analysis and manufacturing, with additional information specific to various industries such as automotive, aerospace, building construction, ship, oil and gas, process plants and others." (http://en.wikipedia.org/wiki/ISO_10303)
One of the interesting aspects of ISO 10303 is the numbering of the Parts goes up to Part 1670 (according to the ISO Web site a few minutes ago, http://www.iso.org/iso/search.htm?qt=ISO+10303&searchSubmit=Search&sort=rel&type=simple&published=on). It is NOT an easy Standard to implement, as I discovered when I tried to do so several years ago in a civil engineering context.
Fred
--------------------------------------
Frederic J. Grevin
[log in to unmask]
Office: 212-312-3903
-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]] On Behalf Of Dwight WALLIS
Sent: Thursday, September 15, 2011 12:10 PM
To: [log in to unmask]
Subject: Re: ERMS 'PERM' Records Declaration Process
Fred, some have suggested that the DoD 5015.3-STD Version 3 move to
application-to-application inter-operability makes these systems viable
candidates for long term electronic records storage, since the
inter-operability standard ensures the ability to migrate to future
certified systems. I'd be curious to hear your's and others' comments on
this.
--
Dwight Wallis, CRM
Multnomah County Records Management Program
1620 SE 190th Avenue
Portland, OR 97233
ph: (503)988-3741
fax: (503)988-3754
[log in to unmask]
List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]
List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]
|
