<font color='black' size='2' face='arial'>Mike,
<div>I concede the DAI has been open and sharing. However, I have not really that transparency regarding the review of OAIS comments and suggested revisions. Or . . I just needed to be smacked upside the head to realize the full implications of where the OAIS revision was going.</div>
<div><br>
</div>
<div>To address your questions below:</div>
<div><br>
</div>
<div>I am not opposed to <span style="color: rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 14.6667px;">any interoperable architecture or protocols effort in digital preservation</span><span style="color: rgb(31, 73, 125); font-size: 14.6667px;"><font face="Arial, Helvetica, sans-serif">.</font></span><span style="color: rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 14.6667px;"> </span><span style="color: rgb(31, 73, 125); font-size: 14.6667px;"><font face="Arial, Helvetica, sans-serif">I am not opposed to </font></span><span style="color: rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 14.6667px;"> any such data architecture compatible with OAIS processes</span><span style="color: rgb(31, 73, 125); font-size: 14.6667px;"><font face="Arial, Helvetica, sans-serif">.</font></span></div>
<div><span style="color: rgb(31, 73, 125); font-size: 14.6667px;"><font face="Arial, Helvetica, sans-serif"><br>
</font></span></div>
<div>I am for retaining the reference model as just that - a broad, high level schema sitting above any specific repository or community's application. ISO 16363 illustrates how an interoperable architecture schema can be achieved. ISO 16363 is "nested" below the RM-OAIS as a/the specific implementation of the call for certification. ISO 16919 is similarly nested as the specific way to conduct the certification audit for digital preservation information systems.</div>
<div><br>
</div>
<div>I am not against the architecture concept as a concept and model. My vision would be a similar nesting for any architecture schema(s). This is where any interoperable architecture or protocol should be - as a unique ISO standard. It must clearly show non scientific communities, especially the cultural heritage digital preservation efforts, how their efforts would be included.</div>
<div><br>
</div>
<div>Perhaps what I am envisioning is a three tier approach. Tier One is the RM-OAIS. Tier Two is the nested efforts such as ISO 16363 and ISO 16919 and any interoperable protocol(s). Tier Three is/are the community specific architecture/protocol implementations, which or may not be ISO standards. I stress the plural because the needs of the diverse communities are just that, diverse. I just do not see how an architecture for any one of the space sciences could be adopted, without change, by the airplane manufacturers, the drug makers or the financial communities.<br>
<br>
Vint Cerf comes at this from a different perspective. We have not been building a single, tightly bundled underlying structural protocol (such as TCP/IP) thatrequires every community to get "on board" the same way. We have consciously been building a looser approach that allows each community to accept and adopt the core (RM-OAIS) and add its own embellishments or definitions, a blending of efforts enhancing digital preservation. There are still many folks who dislike "ingest" and immediately say that is what we call "accessioning" or whatever specific term they use for bringing digital objects into their digital preservation environment. As digital preservation sites proliferate and communities have even less need to interoperate, the need for a single architecture diminishes. Some communities will be able to impose a single architecture; others never will be able to do so.</div>
<div><br>
</div>
<div>Hopefully this gives you a better idea of where I am on this.<br>
<br>
<div style="font-family:arial,helvetica;font-size:10pt;color:black">-----Original Message-----<br>
From: Mike Kearney <kearneysolutions@gmail.com><br>
To: 'MOIMS-Data Archive Ingestion' <moims-dai@mailman.ccsds.org><br>
Sent: Sun, Mar 11, 2018 9:09 pm<br>
Subject: Re: [Moims-dai] OAIS and the OAIS Architecture<br>
<br>
<div id="AOLMsgPart_1.2_ae5867c4-4c38-41d4-aef6-b6617ce948f0">
<style scoped="">#AOLMsgPart_1.2_ae5867c4-4c38-41d4-aef6-b6617ce948f0 td{color: black;} @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;}.aolReplacedBody p.aolmail_MsoNormal,.aolReplacedBody li.aolmail_MsoNormal,.aolReplacedBody div.aolmail_MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman",serif;}.aolReplacedBody a:link,.aolReplacedBody span.aolmail_MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;}.aolReplacedBody a:visited,.aolReplacedBody span.aolmail_MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;}.aolReplacedBody p.aolmail_aolmailmsonormal,.aolReplacedBody li.aolmail_aolmailmsonormal,.aolReplacedBody div.aolmail_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;}.aolReplacedBody p.aolmail_aolmailmsochpdefault,.aolReplacedBody li.aolmail_aolmailmsochpdefault,.aolReplacedBody div.aolmail_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;}.aolReplacedBody span.aolmail_aolmailmsohyperlink {mso-style-name:aolmail_msohyperlink;}.aolReplacedBody span.aolmail_aolmailmsohyperlinkfollowed {mso-style-name:aolmail_msohyperlinkfollowed;}.aolReplacedBody p.aolmail_aolmailmsonormal1,.aolReplacedBody li.aolmail_aolmailmsonormal1,.aolReplacedBody div.aolmail_aolmailmsonormal1 {mso-style-name:aolmail_msonormal1; margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;}.aolReplacedBody span.aolmail_aolmailmsohyperlink1 {mso-style-name:aolmail_msohyperlink1; mso-style-priority:99; color:#0563C1; text-decoration:underline;}.aolReplacedBody span.aolmail_aolmailmsohyperlinkfollowed1 {mso-style-name:aolmail_msohyperlinkfollowed1; mso-style-priority:99; color:#954F72; text-decoration:underline;}.aolReplacedBody span.aolmail_EmailStyle24 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:#1F497D;}.aolReplacedBody .aolmail_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;}.aolReplacedBody div.aolmail_WordSection1 {page:WordSection1;}</style>
<div lang="EN-US" class="aolReplacedBody">
<div class="aolmail_WordSection1">
<div class="aolmail_MsoNormal"><a name="aolmail__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. </span></a></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></div>
<div class="aolmail_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. </span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></div>
<div class="aolmail_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? </span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></div>
<div class="aolmail_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. </span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></div>
<div class="aolmail_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. </span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></div>
<div class="aolmail_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. </span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></div>
<div class="aolmail_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. </span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> -=- Mike</span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Mike Kearney</span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Huntsville, Alabama, USA</span></div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></div>
<div class="aolmail_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 [<a href="mailto:moims-dai-bounces@mailman.ccsds.org?">mailto:moims-dai-bounces@mailman.ccsds.org</a>] <b>On Behalf Of </b>Bruce Ambacher<br>
<b>Sent:</b> Sunday, March 11, 2018 12:10 PM<br>
<b>To:</b> moims-<a href="mailto:dai@mailman.ccsds.org">dai@mailman.ccsds.org</a><br>
<b>Subject:</b> Re: [Moims-dai] OAIS and the OAIS Architecture</span></div>
<div class="aolmail_MsoNormal"> </div>
<div class="aolmail_MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Mike, </span></div>
<div>
<div class="aolmail_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.</span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> </span></div>
</div>
<div>
<div class="aolmail_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.</span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> </span></div>
</div>
<div>
<div class="aolmail_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.</span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> </span></div>
</div>
<div>
<div class="aolmail_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.</span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> </span></div>
</div>
<div>
<div class="aolmail_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>
</span></div>
<div>
<div class="aolmail_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 target="_blank" rel="noopener noreferrer" href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a>><br>
To: 'MOIMS-Data Archive Ingestion' <<a target="_blank" rel="noopener noreferrer" 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</span></div>
<div id="aolmail_AOLMsgPart_1.2_84c1d438-7a38-46cf-9970-38072fd5ad81">
<div>
<div>
<div class="aolmail_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. </span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span></div>
</div>
<div>
<div class="aolmail_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: </span></div>
</div>
<div style="margin-left:.25in">
<div class="aolmail_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;</span></div>
</div>
<div style="margin-left:.25in">
<div class="aolmail_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. </span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span></div>
</div>
<div>
<div class="aolmail_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. </span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> -=- Mike</span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Mike Kearney</span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Huntsville, Alabama, USA</span></div>
</div>
<div>
<div class="aolmail_MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span></div>
</div>
</div>
</div>
<div class="aolmail_MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">_______________________________________________ MOIMS-DAI mailing list MOIMS-<a target="_blank" rel="noopener noreferrer" href="mailto:DAI@mailman.ccsds.org">DAI@mailman.ccsds.org</a> <a target="_blank" rel="noopener noreferrer" href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai</a> </span></div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________
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>
</div>
</div>
</font>