<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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
p.aolmailmsonormal, li.aolmailmsonormal, div.aolmailmsonormal
{mso-style-name:aolmail_msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.aolmailmsochpdefault, li.aolmailmsochpdefault, div.aolmailmsochpdefault
{mso-style-name:aolmail_msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.aolmailmsohyperlink
{mso-style-name:aolmail_msohyperlink;}
span.aolmailmsohyperlinkfollowed
{mso-style-name:aolmail_msohyperlinkfollowed;}
p.aolmailmsonormal1, li.aolmailmsonormal1, div.aolmailmsonormal1
{mso-style-name:aolmail_msonormal1;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.aolmailmsohyperlink1
{mso-style-name:aolmail_msohyperlink1;
mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.aolmailmsohyperlinkfollowed1
{mso-style-name:aolmail_msohyperlinkfollowed1;
mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle24
{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'>Bruce, I highly respect your experience in the community, and I appreciate that you took the time to provide your insight. <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'>I have to say that I’m surprised by the response, though, because I thought that even for folks who have not been in the meetings or telecons, we have explained the rationale and background for this effort in emails with presentation material, minutes, etc. I thought we had pretty good consensus that developing architecture and protocols for interoperability was the next important step for developing a healthier and longer-lasting digital preservation ecosystem. <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'>Just to make sure I understand your message… you’re not only against the term “OAIS Architecture”, you’re against any interoperable architecture or protocols effort in digital preservation? Against any such data architecture compatible with OAIS processes? <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'>When Vint Cerf brought the discussion to me and to the DAI WG about the need for interoperability in the digital preservation archive world, as a newcomer to the group, I was immediately struck by the “gap” that existed in the arena. It’s totally beyond me how adding a capability for improved interoperability can “diminish” OAIS or the work that has gone before. I’ll quickly concede that I don’t have as much experience in this arena as senior experts like you. But I think that, in turn, does not diminish the obvious benefits that some new measure of interoperability between archival IT systems would bring. It’s exactly the “forest of architectures” (I would say forests, plural) that is a contributing obstacle to long-term access. A ubiquitous protocol (ubiquitous like TCP/IP) can only improve long-term access to preserved assets. And while it won’t be imposed on the diverse communities, it will be available for those that recognize the benefits and begin a migration towards it. <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'>In terms of the feasibility or chance of success, I think we’ll just have to get farther downstream. So far nobody else has raised that as a concern. I believe we need interoperable protocols and interfaces, and I am convinced that it would be a mistake to start work on them without having an overall data architecture concept. So that’s why we’re starting with architecture discussions. <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'>So, that’s my high-level perspective, expressed frequently in the DAI WG. And the subject of meetings with other external entities (OMG, IIPC) and the subject of papers at several upcoming conferences this year. So if there is a problem with this work being done in the DAI WG, we need to resolve that issue quickly. <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'>If I’m overreacting, or misinterpreting, I apologize. If you objection is only with the name “OAIS Architecture”, that’s considerably easier to fix. We’ll be discussing that at the next DAI WG telecon, I’m sure. <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>Bruce Ambacher<br><b>Sent:</b> Sunday, March 11, 2018 12:10 PM<br><b>To:</b> 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><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>Mike, <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>I have not been a part of the DAI weekly meetings as I am no longer directly involved in digital preservation systems. But as an original OAIS team member, a retired digital preservation system manager, NARA's representative to several federal data communities, a team member on the development of NARA's Electronic records Archives, and an information studies visiting professor, I think i can make an overall comment.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>Since its initial development, beginning in 1995, through adoption, and a ten year review, all involved were quite vocal in insisting that OAIS was NOT an architecture. To turn a position held for nearly a quarter century 180 degrees is unwise and endangers its credibility. The greatest value of OAIS was its simplicity, its plain text, its ability to be understood at every level of digital preservation, and its use of high level components to allow individual communities to be compliant and to utilize their own architecture below that framework.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>I also believe that effort will diminish the OAIS. Beneath it is a forest of "architectures" developed by different communities to meet their community needs. Too be successful you would have to eliminate/incorporate every such architecture into an over riding super architecture. The end result would be an architecture that communities might pay lip service to but it would be an architecture so complex that most such communities would reject it and continue doing what they were doing.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>I believe the proper place for such an architecture is in annexes to the standard or in a separate standard. I also should point out that OAISIS is already in use in the cultural heritage digital preservation community and to utilize that would create both confusion and resentment - just one example of how changing something has unexpected consequences.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>You note: </span><span style='font-size:7.0pt;color:black'> "</span><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>The use of the term “OAIS Architecture” should not be considered intended to change anything about the OAIS Reference Model or certification thereof" If that is true why do it, especially when the consequences could be different than expected? You also note: "</span><span style='font-size:7.0pt;color:black'> </span><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>If use of the term “OAIS Architecture” make people think it will change OAIS, then maybe we need a new term." I believe the answer is more than a "Maybe." It is a definite.<br><br><o:p></o:p></span></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>-----Original Message-----<br>From: Mike Kearney <<a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a>><br>To: 'MOIMS-Data Archive Ingestion' <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>><br>Sent: Sat, Mar 10, 2018 10:29 pm<br>Subject: [Moims-dai] OAIS and the OAIS Architecture<o:p></o:p></span></p><div id="AOLMsgPart_1.2_84c1d438-7a38-46cf-9970-38072fd5ad81"><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>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></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>The main points you should take away from this discussion are: <o:p></o:p></span></p></div><div style='margin-left:.25in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.0pt;font-family:Symbol;color:black'>·</span><span style='font-size:7.0pt;color:black'> </span><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>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></span></p></div><div style='margin-left:.25in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.0pt;font-family:Symbol;color:black'>·</span><span style='font-size:7.0pt;color:black'> </span><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>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></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>I would prefer to stick with “OAIS Architecture,” but we can discuss other options. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> -=- Mike<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>Mike Kearney<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>Huntsville, Alabama, USA<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> <o:p></o:p></span></p></div></div></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>_______________________________________________ MOIMS-DAI mailing list MOIMS-<a href="mailto:DAI@mailman.ccsds.org">DAI@mailman.ccsds.org</a> <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></span></p></div></div></div></body></html>