<div style="FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 12px"><div>I think we are heading toward the same solution and order of priorities. </div><div> </div><div> </div><div style="border-top:1px solid #bcbcbc;margin:5px 0px;"></div><span style="font-size:12;font-family:arial;color:#000000;">On 04/22/16, <span>Mike Kearney<kearneysolutions@gmail.com></span> wrote:</span><div> </div><div style="font-size:12;font-family:arial;color:#000000;"><div class="WordSection1"><p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><a name="_MailEndCompose"><!--[if !supportLists]--><span lang="EN-GB" style="font-size:11.0pt;font-family:Wingdings"><span style="mso-list:Ignore">Ø<span style="font:7.0pt "Times New Roman"">  </span></span></span><!--[endif]--><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">I don’t think that the intention was to say that ALL repositories want to be interoperable.  </span></a></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </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.  </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </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.  </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </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.  </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p><p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span lang="EN-GB" style="font-size:11.0pt;font-family:Wingdings"><span style="mso-list:Ignore">Ø<span style="font:7.0pt "Times New Roman"">  </span></span></span><!--[endif]--><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">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 lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </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?  </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">   -=- Mike</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Mike Kearney</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Huntsville, Alabama, USA</span></p></div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </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 class="parsedEmail" href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">moims-dai-bounces@mailman.ccsds.org</a> [<a class="parsedLink" 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 class="parsedEmail" 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</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Bruce</span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">I don’t think that the intention was to say that ALL repositories want to be interoperable.  </span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">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. </span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regards</span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">..David </span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </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 class="parsedEmail" href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">moims-dai-bounces@mailman.ccsds.org</a> [<a class="parsedEmail" href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">mailto:moims-dai-bounces@mailman.ccsds.org</a>] <b>On Behalf Of </b><a class="parsedEmail" 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 class="parsedEmail" 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</span></p><p class="MsoNormal"><span lang="EN-GB"> </span></p><div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">If I may make an observation:</span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">1. All of this presumes all digital repositories want to be interoperable, which they may not.</span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">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.</span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">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.</span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">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></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">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.</span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p></div><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p></div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">On 04/20/16, David Giaretta<<a class="parsedEmail" href="mailto:david@giaretta.org" target="_blank">david@giaretta.org</a>> wrote:</span></p><div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p></div><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Any objections/updates/additions/corrections?</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Regards</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">..David</span></p></div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></p><div align="center" class="MsoNormal" style="text-align:center"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><hr align="center" size="1" width="100%" /></span></div><p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><br />_______________________________________________<br />Moims-dai mailing list<br /><a class="parsedEmail" 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></span></p></div></div></div><br /><hr size="1" /><br />_______________________________________________<br />Moims-dai mailing list<br /><a class="parsedEmail" href="mailto:Moims-dai@mailman.ccsds.org" target="_blank">Moims-dai@mailman.ccsds.org</a><br /><a class="parsedLink" href="http://mailman.ccsds.org/mailman/listinfo/moims-dai" target="_blank">http://mailman.ccsds.org/mailman/listinfo/moims-dai</a><br /></div></div>