<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>In terms of the naming convention for the architecture… I would like to keep this as an open discussion for a while longer. The term “Framework” is quite a bit overused nowadays (The CCSDS management “framework” for example). <o:p></o:p></span></a></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>My opinion was that OAIS would benefit from an interoperable architecture, but if the group wants to have a terminology divide between OAIS and this digital preservation architecture, then so be it. I would encourage the group to discuss this a bit further, though. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Bob, your discussion about whether there can be multiple frameworks for OAIS interoperability… If the multiple frameworks are not interoperable with each other… that would be a really bad thing. Similar to having two OAIS Reference Models that contradict each other. And if the multiple frameworks for OAIS interoperability are interoperable with each other… I think that’s one framework, not two. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Mike Kearney<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Huntsville, Alabama, USA<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></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'> MOIMS-DAI [mailto:moims-dai-bounces@mailman.ccsds.org] <b>On Behalf Of </b>Robert Downs<br><b>Sent:</b> Sunday, March 11, 2018 3:29 PM<br><b>To:</b> MOIMS-Data Archive Ingestion <moims-dai@mailman.ccsds.org><br><b>Subject:</b> Re: [Moims-dai] OAIS and the OAIS Architecture<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>I agree with Bruce's concerns and believe that we need to be very careful that proposing and naming a new design artifact does not cause confusion. I also agree with John's concerns and believe that it should be done in a way that does not imply that a proposed design artifact is a requirement for certification of OAIS compliance. Using a term like OAIS Interoperability Framework, which David proposed, might be a step in the right direction, as compared to the earlier term. However, considering the variety of diverse communities that have embraced the OAIS Reference Model, I wonder whether using a term, such as OAIS Interoperability Framework, would imply that there is no room for other frameworks for OAIS interoperability. <o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>Thanks,<o:p></o:p></p></div><p class=MsoNormal>Bob<o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><p class=MsoNormal>Robert R. Downs, PhD<br>Senior Digital Archivist and Senior Staff Associate Officer of Research<br>Acting Head of Cyberinfrastructure and Informatics Research and Development<br>Center for International Earth Science Information Network (CIESIN),<br>The Earth Institute, Columbia University<br>P.O. Box 1000, 61 Route 9W, Palisades, NY 10964 USA<br>Voice: 845-365-8985; fax: 845-365-8922<br>E-mail: <a href="mailto:rdowns@ciesin.columbia.edu" target="_blank">rdowns@ciesin.columbia.edu</a><br>Columbia University CIESIN Web site: <a href="http://www.ciesin.columbia.edu" target="_blank">http://www.ciesin.columbia.edu</a><br>ORCID: 0000-0002-8595-5134<o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Sun, Mar 11, 2018 at 3:07 PM, John Garrett <<a href="mailto:garrett@his.com" target="_blank">garrett@his.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Hi,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>That sounds good to me.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>I agree that OAIS Architecture sounds too much like it is a required architecture to be OAIS compliant. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>It also then starts to be misunderstood as required to be certified.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>However OAIS-Interoperability Framework sounds less like a requirement and more like a desirable feature that archives would want.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Peace and joy,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>-JOhn </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a name="m_-101362742517210765__MailEndCompose"><span style='color:#1F497D'> </span></a><o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> MOIMS-DAI [mailto:<a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">moims-dai-bounces@mailman.ccsds.org</a>] <b>On Behalf Of </b>David Giaretta<br><b>Sent:</b> Sunday, March 11, 2018 1:22 PM<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] OAIS and the OAIS Architecture<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB>Would it be better to call the new work an OAIS Interoperability Framework (OAIS-IF)</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB>..David</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> MOIMS-DAI <<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> 11 March 2018 03:29<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> [Moims-dai] OAIS and the OAIS Architecture<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>DAI WG members: After last Tuesday’s discussion, I realized that we have an issue at least with terminology for the new architecture effort. So I’m attaching a short writeup for your reading pleasure and discussion during the next telecon. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The main points you should take away from this discussion are: <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.25in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>The use of the term “OAIS Architecture” should not be considered intended to change anything about the OAIS Reference Model or certification thereof, and;<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.25in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>If use of the term “OAIS Architecture” make people think it will change OAIS, then maybe we need a new term. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I would prefer to stick with “OAIS Architecture,” but we can discuss other options. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> -=- Mike<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Mike Kearney<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Huntsville, Alabama, USA<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>MOIMS-DAI mailing list<br><a href="mailto:MOIMS-DAI@mailman.ccsds.org">MOIMS-DAI@mailman.ccsds.org</a><br><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai" target="_blank">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>