<div dir="ltr">Well said.<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Mark Conrad<br>NARA Information Services</div>
<div>IAS<br>The National Archives and Records Administration<br>Erma Ora Byrd
Conference and Learning Center<br>Building 494 Second Floor<br>610 State Route
956<br>Rocket Center, WV 26726<br><br>Phone: 304-726-7820<br>Fax:
304-726-7802<br>Email: <a href="mailto:mark.conrad@nara.gov" target="_blank">mark.conrad@nara.gov</a> <br><br></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Apr 26, 2016 at 1:27 AM, John Garrett <span dir="ltr"><<a href="mailto:garrett@his.com" target="_blank">garrett@his.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hi,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I’m very much in support of developing standards for interoperable archives. But as much as I am in support of that, I don’t really know what others mean by that or what they are looking for. I think I need to see some user requirements/storyboards for what interoperability would look like. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><br>I think a lot of technical interoperability issues have been solved. Some others still need to be, but people are working on them. I think the biggest interoperability issues are the financial and political layers from Vint’s IIPC talk.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">There are lots of standards at the lower levels that are available at lower layers and certain profiles of these are used in certain domains for interoperability there. But I think technical standards are very reliant on markets and marketing of solutions and on technological advancements that allow new technical standards to overtake the old ones.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I think that is why the OAIS and auditing standards are so important. They help manage those changes.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Wishing you prosperity and peace,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">-JOhn<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><a name="m_-2601515901622657451__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></a></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">moims-dai-bounces@mailman.ccsds.org</a> [mailto:<a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">moims-dai-bounces@mailman.ccsds.org</a>] <b>On Behalf Of </b>Mike Kearney<br><b>Sent:</b> Friday, April 22, 2016 9:50 AM<br><b>To:</b> 'MOIMS-Data Archive Ingestion' <<a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">moims-dai@mailman.ccsds.org</a>><br><b>Subject:</b> RE: [Moims-dai] Notes on meeting with Vint Cerf<u></u><u></u></span></p></div></div><p class="MsoNormal"><u></u> <u></u></p><p><u></u><span style="font-size:11.0pt;font-family:Wingdings" lang="EN-GB"><span>Ø<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB">I don’t think that the intention was to say that ALL repositories want to be interoperable. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Absolutely right. If a repository is not interoperable, it should be because that repository <b><i>chooses</i></b> to be non-interoperable. Not because there is no choice to be interoperable because of industry divergence and broad incompatibilities. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">In my opinion the business case for interoperability can be entirely made by the cross-discipline research scenario where future researchers need to access multiple discipline databases, multiple mission databases, etc. in order to get synergized results to make new discoveries. But of course there are also other business cases for the standardization that leads to interoperability, such as commercial products, cost reduction, “many eyes on the problem”, etc. All of the benefits of standardization, the greatest of which is interoperability. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Totally understand that there are many diverse and obscure databases and archives that will never be able to line up with an interoperability standard. But if we fail to produce the standard, then we (the standards community) have produced the problem, not them. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p><u></u><span style="font-size:11.0pt;font-family:Wingdings" lang="EN-GB"><span>Ø<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">4. We need to assert our original goal of developing a standard and an audit process to evaluate digital repositories against that standard as to their ability to operate a digital repository that can accept digital data, preserve it, and provide it in a usable form to a user when requested. If we cannot find or develop that market, we certainly cannot develop Vint Cerf's under developed concepts. </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Absolutely. That doesn’t contradict the need to set interoperable standards as the next goal, does it? To better develop those under-developed concepts? <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> -=- Mike<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Mike Kearney<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Huntsville, Alabama, USA<u></u><u></u></span></p></div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">moims-dai-bounces@mailman.ccsds.org</a> [<a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">mailto:moims-dai-bounces@mailman.ccsds.org</a>] <b>On Behalf Of </b>David Giaretta<br><b>Sent:</b> Friday, April 22, 2016 6:36 AM<br><b>To:</b> 'MOIMS-Data Archive Ingestion' <<a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">moims-dai@mailman.ccsds.org</a>><br><b>Subject:</b> RE: [Moims-dai] Notes on meeting with Vint Cerf<u></u><u></u></span></p></div></div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB">Hi Bruce<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB">I don’t think that the intention was to say that ALL repositories want to be interoperable. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB">The way I interpreted it was that in order to increase use of the standards and also to add value to what is being preserved by increasing its usefulness – interoperability is one important way of doing that. I think we should take that on board and try to show how DAI/RAC standards can be used both for preservation and also for adding value. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB">Regards<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB">..David <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">moims-dai-bounces@mailman.ccsds.org</a> [<a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">mailto:moims-dai-bounces@mailman.ccsds.org</a>] <b>On Behalf Of </b><a href="mailto:bambacher@verizon.net" target="_blank">bambacher@verizon.net</a><br><b>Sent:</b> 20 April 2016 20:38<br><b>To:</b> <a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">moims-dai@mailman.ccsds.org</a><br><b>Subject:</b> Re: [Moims-dai] Notes on meeting with Vint Cerf<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">If I may make an observation:<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">1. All of this presumes all digital repositories want to be interoperable, which they may not.<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">2. Vint Cerf appears to seriously minimize the number of spplications and software used to create digital records requiring preservation. NARA's scope of the problem study found 15,000+ applications and software routines in use in the federal government. It is hard enough to crosswalk between geospatial applications let alone cross walking between geospatial applications and office applications and CAD-CAM applications. I could be over reaching his intentions but even if he only called for inter-operability within a specific discipline, designated community, or data type that is a large problem.<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">3. Recall the approach of a few test audit sites that ingested data only in a single pre-approved SPSS format, essentially frozen in 30+ years old structure. They dictated to their Designated Community. They would not fit Mr. Cerf's generic protocol for sharing data.<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">4. We need to assert our original goal of developing a standard and an audit process to evaluate digital repositories against that standard as to their ability to operate a digital repository that can accept digital data, preserve it, and provide it in a usable form to a user when requested. If we cannot find or develop that market, we certainly cannot develop Vint Cerf's under developed concepts. <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">5. We should obviously respond, thank him, state our position and how it fits his challenge. But, unless he can provide funding and/or FTE to pursue the issue, it is beyond our scope of effort.<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"> <u></u><u></u></span></p></div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">On 04/20/16, David Giaretta<<a href="mailto:david@giaretta.org" target="_blank">david@giaretta.org</a>> wrote:<u></u><u></u></span></p><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"> <u></u><u></u></span></p></div><div><div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">Any objections/updates/additions/corrections?<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"> <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">Regards<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"> <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB">..David<u></u><u></u></span></p></div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"><u></u> <u></u></span></p><div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"><hr align="center" size="1" width="100%"></span></div><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-GB"><br>_______________________________________________<br>Moims-dai mailing list<br><a href="mailto:Moims-dai@mailman.ccsds.org" target="_blank">Moims-dai@mailman.ccsds.org</a><br><a href="http://mailman.ccsds.org/mailman/listinfo/moims-dai" target="_blank">http://mailman.ccsds.org/mailman/listinfo/moims-dai</a><u></u><u></u></span></p></div></div></div></div><br>_______________________________________________<br>
Moims-dai mailing list<br>
<a href="mailto:Moims-dai@mailman.ccsds.org">Moims-dai@mailman.ccsds.org</a><br>
<a href="http://mailman.ccsds.org/mailman/listinfo/moims-dai" rel="noreferrer" target="_blank">http://mailman.ccsds.org/mailman/listinfo/moims-dai</a><br>
<br></blockquote></div><br></div>