<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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.aolmailaolmailmsonormal, li.aolmailaolmailmsonormal, div.aolmailaolmailmsonormal
{mso-style-name:aolmail_aolmailmsonormal;
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.aolmailaolmailmsochpdefault, li.aolmailaolmailmsochpdefault, div.aolmailaolmailmsochpdefault
{mso-style-name:aolmail_aolmailmsochpdefault;
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.aolmailaolmailmsonormal1, li.aolmailaolmailmsonormal1, div.aolmailaolmailmsonormal1
{mso-style-name:aolmail_aolmailmsonormal1;
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;}
span.aolmailaolmailmsohyperlink
{mso-style-name:aolmail_aolmailmsohyperlink;}
span.aolmailaolmailmsohyperlinkfollowed
{mso-style-name:aolmail_aolmailmsohyperlinkfollowed;}
span.aolmailaolmailmsohyperlink1
{mso-style-name:aolmail_aolmailmsohyperlink1;}
span.aolmailaolmailmsohyperlinkfollowed1
{mso-style-name:aolmail_aolmailmsohyperlinkfollowed1;}
span.aolmailemailstyle24
{mso-style-name:aolmail_emailstyle24;}
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.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle33
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#993366;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1272972207;
mso-list-type:hybrid;
mso-list-template-ids:1357391560 -1563384136 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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:#993366'>Thanks, Bruce, that really does clarify a fair amount. I really thought that you were saying that any OAIS-supporting architecture standard is a bad idea. <o:p></o:p></span></a></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:Wingdings;color:#993366'><span style='mso-list:Ignore'>Ø<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'>I just needed to be smacked upside the head to realize the full implications of where the OAIS revision was going.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'>This whole discussion is outside of the OAIS revision. The OAIS RM 5-year update is being done without any consideration of this or any other data architecture. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'>One comment on your tiers two and three. You have protocols in tier two and architecture in tier three. Before protocols (or interfaces, bindings, APIs or whatever they turn out to be) can be developed, you have to start with a coherent end-to-end architecture view. So (I think) that means Architecture is a second tier and protocols/bindings/APIs are the third (following) tier. Completely agree that the OAIS RM is tier one. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'>You’re right that TCP/IP is not a perfect analogy, because it’s at the network layer and archives are at the application layer. But that doesn’t drive a requirement to have only the “looser approach” for application layer interfaces. Applications can have standard interfaces too, when it’s a smart strategic thing to do. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'>Understand your concern that one architecture won’t meet the needs of all designated communities. We are saying that we can constrain the requirements of specific designated communities to the plug-in or protocol that is specific to their designated communities’ archive. We may be wrong in some cases, even as much as 50% of the cases. But the extraordinary benefits make it worth trying, and maybe we’ll hit 95% as more designated communities see the benefits of interoperability and jump on board. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'>In any case, we’re planning on a lot of peer reviews, so those designated communities are going to get their chances to speak up. I can say that when I spoke to the RDA on this, there were only very positive responses. We’ll see how other communities speak up as we press forward with the program. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'>Mike Kearney<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'>Huntsville, Alabama, USA<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#993366'><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> Monday, March 12, 2018 3:03 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 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.<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'>To address your questions below:<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 am not opposed to </span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>any interoperable architecture or protocols effort in digital preservation</span><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:#1F497D'>.</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:#1F497D'>I am not opposed to </span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> any such data architecture compatible with OAIS processes</span><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:#1F497D'>.</span><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'><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 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.<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 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.<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'>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.<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'>Hopefully this gives you a better idea of where I am on this.<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: Sun, Mar 11, 2018 9:09 pm<br>Subject: Re: [Moims-dai] OAIS and the OAIS Architecture<o:p></o:p></span></p><div id="AOLMsgPart_1.2_ae5867c4-4c38-41d4-aef6-b6617ce948f0"><div><div><p class=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><span style='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:#1F497D'> </span><span style='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:#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><span style='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:#1F497D'> </span><span style='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:#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><span style='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:#1F497D'> </span><span style='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:#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><span style='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:#1F497D'> </span><span style='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:#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><span style='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:#1F497D'> </span><span style='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:#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><span style='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:#1F497D'> </span><span style='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:#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><span style='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:#1F497D'> </span><span style='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:#1F497D'> -=- Mike</span><span style='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:#1F497D'> </span><span style='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:#1F497D'>Mike Kearney</span><span style='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:#1F497D'>Huntsville, Alabama, USA</span><span style='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:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> 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><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='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'>Mike, </span><span style='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'>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><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div><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.</span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div><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.</span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div><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.</span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div><div><div style='margin-bottom:12.0pt'><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.</span><span style='color:black'><o:p></o:p></span></p></div><div><div style='margin-bottom:12.0pt'><p class=MsoNormal><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" target="_blank">kearneysolutions@gmail.com</a>><br>To: 'MOIMS-Data Archive Ingestion' <<a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">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><span style='color:black'><o:p></o:p></span></p></div><div id="aolmail_AOLMsgPart_1.2_84c1d438-7a38-46cf-9970-38072fd5ad81"><div><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. </span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div><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: </span><span style='color:black'><o:p></o:p></span></p></div></div><div style='margin-left:.25in'><div><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;</span><span style='color:black'><o:p></o:p></span></p></div></div><div style='margin-left:.25in'><div><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. </span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div><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. </span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> -=- Mike</span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>Mike Kearney</span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>Huntsville, Alabama, USA</span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div></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" target="_blank">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> </span><span style='color:black'><o:p></o:p></span></p></div></div></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>