<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.gmail-m-2012385482553399736m-264577622854671377gmail-msocommenttext, li.gmail-m-2012385482553399736m-264577622854671377gmail-msocommenttext, div.gmail-m-2012385482553399736m-264577622854671377gmail-msocommenttext
{mso-style-name:gmail-m_-2012385482553399736m_-264577622854671377gmail-msocommenttext;
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.gmail-m-2012385482553399736m-264577622854671377gmail-msocommentreference
{mso-style-name:gmail-m_-2012385482553399736m_-264577622854671377gmail-msocommentreference;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
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><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Comments below.<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></a></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>Mark Conrad<br><b>Sent:</b> Monday, September 10, 2018 12:10 PM<br><b>To:</b> MOIMS-Data Archive Interoperability <moims-dai@mailman.ccsds.org><br><b>Cc:</b> David Giaretta <david@giaretta.info><br><b>Subject:</b> Re: [Moims-dai] Response to rejection of SC234<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>" <span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>All the components of the AIP would now be focused on the CDO which in my view is the thing that we really want to focus most on preserving."</span><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Representation Information is defined as: The information that maps a Data Object into more meaningful concepts so that the Data Object may be understood in ways exemplified by Preservation Objectives.</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Without the Representation Information the CDO will become meaningless over time. I believe that the previous versions of OAIS which made the Content Information the original target of preservation are correct.<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>JGG: I agree that RepInfo is important for preservation. It is still required to be part of the AIP. In most cases I don’t think there is any real reason to maintain the RepInfo if the CDO is lost/corrupted. I do think that in many cases you would still want to keep the CDO if the RepInfo were lost/corrupted. Occasionally/often RepInfo can be recreated if it is lost/corrupted (or discovered if it did not exist, for example uncovering meaning of Rosetta Stone). Rarely can CDO be recreated. Of course your mileage may differ.<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>" <span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;background:white'>But these other things are not the primary focus of long-term preservation for this OAIS."</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Representation Information has to be part of the primary focus of long-term preservation. Without it, the CDO will become meaningless in the medium to long term. The best time to gather the initial version of the RepInfo - as we have discussed frequently - is at or near the time of creation of the CDO.<o:p></o:p></p></div><div><p class=MsoNormal><span style='color:#1F497D'>JGG: I totally agree with the need for RepInfo and it is still required for the AIP.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><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></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;background:white'>"Any archive that was OAIS compatible before will remain OAIS compatible. I.e. if you had fixity/provenance/… on Content Info (CDO+RepInfo) then you have sufficient fixit/provenance/… on the CDO.</span> "<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This misses the point. You cannot have long term preservation without RepInfo being part of the original target of preservation.<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>JGG: I agree that RepInfo is needed in the AIP for long-term preservation. I don’t agree that PDI is always needed for the RepInfo. I don’t agree that RepInfo is the usually the focus of long-term preservation in the same sense that the original data in the CDO is the focus of long-term preservation. I also believe that the CDO is originally created. Hopefully RepInfo is concurrently created, but in reality often is not and if not, hopefully it will be added as soon as possible. But in many cases, RepInfo is “less original”/later in the timeline than creation of the CDO.<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>What is the harm of keeping Content Information as the original target of preservation? I see a number of harms in making just the CDO the original target of preservation. Unless there are compelling reasons to change the original target of preservation - one of the core principles of OAIS - I don't believe it should be changed.<o:p></o:p></p></div><div><p class=MsoNormal><span style='color:#1F497D'>JGG: Certainly we can keep Content Information as original target of creation. OAIS has it defined that way for last 15 years. Although I think most OAIS users have misunderstood the distinction. But I think the change is more correct.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Actually something just occurred to me. There is also a middle option. The changes to make PDI applicable to CDO could still be made while maintaining the definition of Content Info (CDO + RepInfo) as the original target of preservation. Anyone have thoughts on that?<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></div><div><p class=MsoNormal>My two cents.<o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal>Mark <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Mon, Sep 10, 2018 at 10:29 AM, 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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;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='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>First thanks to everyone for the many and robust comments and discussions generated by this thread. It has allowed for a lot of great discussions.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>However, we also need to finish the OAIS updates in the near term. We’re about 2 years in on actively working on these updates and started about 6 months earlier than that when we set up the review site. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Just to focus the discussion, although many issues were brought up, SC#222 just changed the definition of PDI terms to refer them to the CDO rather than the Content Information (CDO+RepInfo).</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Some of my thoughts on this. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>All the components of the AIP would now be focused on the CDO which in my view is the thing that we really want to focus most on preserving.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This does not mean that we don’t preserve other objects that are part of an AIP (that are there to help preserve the CDO). Doesn’t even mean that within the OAIS we don’t preserve other things that are not even in an AIP. But these other things are not the primary focus of long-term preservation for this OAIS.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This does not prevent PDI like objects to be associated with any objects other than the CDO. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Yes, it does change the definition that was in the previous 2 issues. But I don’t think that it will cause any previous users of the OAIS standard any problem. Going this direction is backwards compatible. Any archive that was OAIS compatible before will remain OAIS compatible. I.e. if you had fixity/provenance/… on Content Info (CDO+RepInfo) then you have sufficient fixit/provenance/… on the CDO.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I’m traveling. Hopefully I will be able to connect to the call.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;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='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>-JOhn</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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:</span><a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>moims-dai-bounces@mailman.ccsds.org</span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>] <b>On Behalf Of </b>Mark Conrad<br><b>Sent:</b> Tuesday, September 4, 2018 1:46 PM<br><b>To:</b> MOIMS-Data Archive Interoperability <</span><a href="mailto:moims-dai@mailman.ccsds.org" target="_blank"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>moims-dai@mailman.ccsds.org</span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>><br><b>Subject:</b> Re: [Moims-dai] Response to rejection of SC234</span><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='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I believe Don is correct about the applicability of PDI only to the Content Information (or the Content Data Object per SC 222). If you look at the current definitions for the PDI components, they apply to the Content Information (or the Content Data Object per SC 222).<o:p></o:p></p><div><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='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>Preservation Description Information (PDI</b>): The<b> </b>information which is necessary for adequate preservation of the Content Data Obect (sic) <a href="#m_-2012385482553399736_m_-2645776228546" id="gmail-m_-2012385482553399736m_-264577622854671377gmail-_anchor_1"><span lang=X-NONE style='font-size:8.0pt'>[JG1]</span></a><span class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommentreference><span lang=X-NONE style='font-size:8.0pt'> </span></span>and which can be categorized as Provenance Information, Context Information, Reference Information, Fixity Information, and Access Rights Information.<a name="m_-2012385482553399736_m_-26457762285467" id="gmail-m_-2012385482553399736m_-264577622854671377gmail-_anchor_2"></a><a href="#m_-2012385482553399736_m_-2645776228546"><span lang=X-NONE style='font-size:8.0pt'>[JG2]</span></a><o:p></o:p></p></div><div><p class=MsoNormal style='margin-top:12.0pt;mso-margin-bottom-alt:auto;text-align:justify;line-height:14.0pt'><b>Provenance Information</b>:<b> </b>The information that documents the history of the Content Data Object. This information tells the origin or source of the Content Data Object,<a href="#m_-2012385482553399736_m_-2645776228546" id="gmail-m_-2012385482553399736m_-264577622854671377gmail-_anchor_1"><span lang=X-NONE style='font-size:8.0pt'>[JG1]</span></a><span class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommentreference><span lang=X-NONE style='font-size:8.0pt'> </span></span> any changes that may have taken place since it was originated, and who has had custody of it since it was originated. The Archive is responsible for creating and preserving Provenance Information from the point of Ingest; however, earlier Provenance Information should be provided by the Producer. Provenance Information adds to the evidence to support Authenticity.<o:p></o:p></p><p class=MsoNormal style='margin-top:12.0pt;mso-margin-bottom-alt:auto;text-align:justify;line-height:14.0pt'><b>Context Information</b>:<b> </b>The information that documents the relationships of the Content Data Object to its environment. This includes why the Content Data Object was created and how it relates to other Content Data Objects<a href="#m_-2012385482553399736_m_-2645776228546" id="gmail-m_-2012385482553399736m_-264577622854671377gmail-_anchor_1"><span lang=X-NONE style='font-size:8.0pt'>[JG1]</span></a><span class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommentreference><span lang=X-NONE style='font-size:8.0pt'> </span></span><o:p></o:p></p><div><div><div id="gmail-m_-2012385482553399736m_-264577622854671377gmail-_com_1"><p class=MsoNormal style='margin-top:12.0pt;mso-margin-bottom-alt:auto;line-height:14.0pt'><b>Reference Information</b>:<b> </b>The information that is used as an identifier for the Content Data Object. It also includes identifiers that allow outside systems to refer unambiguously to particular Content Data Object.<a href="#m_-2012385482553399736_m_-2645776228546" id="gmail-m_-2012385482553399736m_-264577622854671377gmail-_anchor_1"><span lang=X-NONE style='font-size:8.0pt'>[JG1]</span></a><span class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommentreference><span lang=X-NONE style='font-size:8.0pt'> </span></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>NOTE: An <a href="#m_-2012385482553399736_m_-2645776228546" id="gmail-m_-2012385482553399736m_-264577622854671377gmail-_anchor_2"><span lang=X-NONE style='font-size:8.0pt'>[JG2]</span></a><span class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommentreference><span lang=X-NONE style='font-size:8.0pt'> </span></span>example of Reference Information is an ISBN.<o:p></o:p></p><p class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommenttext style='margin-bottom:0in;margin-bottom:.0001pt;text-align:justify;line-height:14.0pt'><b>Fixity Information</b>:<b> </b>The information which documents the mechanisms that ensure that the Content Data Object <a href="#m_-2012385482553399736_m_-2645776228546" id="gmail-m_-2012385482553399736m_-264577622854671377gmail-_anchor_1"><span lang=X-NONE style='font-size:8.0pt'>[JG1]</span></a><span class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommentreference><span lang=X-NONE style='font-size:8.0pt'> </span></span>has not been altered in an undocumented manner.<o:p></o:p></p><p class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommenttext style='margin-bottom:0in;margin-bottom:.0001pt;text-align:justify;line-height:14.0pt'><b>Access Rights Information:</b> The information that identifies the access restrictions pertaining to the Content Data Object, <a href="#m_-2012385482553399736_m_-2645776228546" id="gmail-m_-2012385482553399736m_-264577622854671377gmail-_anchor_1"><span lang=X-NONE style='font-size:8.0pt'>[JG1]</span></a><span class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommentreference><span lang=X-NONE style='font-size:8.0pt'> </span></span>including the legal framework, licensing terms, and access control. It contains the access and distribution conditions stated within the Submission Agreement, related to both preservation (by the OAIS) and final usage (by the Consumer). It also includes the specifications for the application of rights enforcement measures.<o:p></o:p></p><p class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommenttext style='margin-bottom:0in;margin-bottom:.0001pt;text-align:justify;line-height:14.0pt'> <o:p></o:p></p><p class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommenttext style='margin-bottom:0in;margin-bottom:.0001pt;text-align:justify;line-height:14.0pt'>Note that in each case the PDI and its components pertain to the Content Information (or the Content Data Object per SC 222). It does not apply to all Information Objects held by the OAIS. David, I believe that you submitted a Suggested Change, or maybe it was just an email thread, to apply the same preservation protocols to all information objects - not just Content Information. This suggestion was rejected by the group if I remember correctly.<o:p></o:p></p><p class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommenttext style='margin-bottom:0in;margin-bottom:.0001pt;text-align:justify;line-height:14.0pt'>Given the above, I am inclined to agree with Don to reverse SC 222.<o:p></o:p></p><p class=gmail-m-2012385482553399736m-264577622854671377gmail-msocommenttext style='margin-bottom:0in;margin-bottom:.0001pt;text-align:justify;line-height:14.0pt'>Mark<o:p></o:p></p></div></div></div></div></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br clear=all><o:p></o:p></p><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Mark Conrad<br>NARA Information Services<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>Systems Engineering Division (IT)<br>The National Archives and Records Administration<br>Erma Ora Byrd Conference and Learning Center<br>Building 494, Room 225<br>610 State Route 956<br>Rocket Center, WV 26726<br><br>Phone: 304-726-7820<br>Fax: 304-726-7802<br>Email: <a href="mailto:mark.conrad@nara.gov" target="_blank">mark.conrad@nara.gov</a> <o:p></o:p></p></div></div></div></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br><span lang=IT>_______________________________________________<br>MOIMS-DAI mailing list<br></span><a href="mailto:MOIMS-DAI@mailman.ccsds.org" target="_blank"><span lang=IT>MOIMS-DAI@mailman.ccsds.org</span></a><span lang=IT><br></span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai" target="_blank"><span lang=IT>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai</span></a><span lang=IT><o:p></o:p></span></p></blockquote></div><p class=MsoNormal><span lang=IT><o:p> </o:p></span></p></div></div></div></div></body></html>