<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>Steve,</p>
<p>I don't have Microsoft and I'm not sure if Libreoffice interprets
the non-standard markup correctly so I didn't want to redline
your document (or Mike's version). <br>
</p>
<p>Some things I noticed: <br>
</p>
<ol>
<li>Section 2.3 Derived Interfaces, lists two package types for
consumers, only one of which is a DIP. This will always be
controversial, and in discussions (last month?) we suggested the
diagrams use "IP" instead of DIP to accommodate all packages
delivered to consumers. This dichotomy should also be mentioned
in Section 2.1 to reflect the distinction between true archived
materials (i.e. derived directly from AIPs) and ancillary data
such as search request responses, scheduling dialogs, or Report
Assistance delivered to the Consumer.
Of course you could leave such dialog or ancillary interactions
outside of the OAISIF altogether, and leave those things to
implementers to solve on their own. I'm not sure they'd
necessarily impact the preservation life cycle.<br>
<br>
</li>
<li>(I know this is a real <i>nit</i>) But book dates, in the
footer and on the title page don't match. <br>
<br>
</li>
<li>Figure 3 Caption (<i>sound it out)</i><br>
</li>
</ol>
<p><br>
</p>
<div class="moz-cite-prefix">On 2020-10-07 10:11 PM,
<a class="moz-txt-link-abbreviated" href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:036b01d69d18$47076050$d51620f0$@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle30
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}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]-->
<div class="WordSection1">
<p class="MsoNormal">Steve, attached are my draft additions to
explain the boundaries of normative material in the
architecture, as we discussed during the telecon on Tuesday.
I turned track changes on, and you’ll find updates only in
sections 1.1 and 1.5. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All, if you’re submitting comments/redlines
to Steve, remember to turn on Track Changes first… they’re off
by default in the copy that Steve sent. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:#002060"> -=- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal">Mike Kearney<span style="color:#002060"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">Huntsville,
Alabama, USA <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> MOIMS-DAI
<a class="moz-txt-link-rfc2396E" href="mailto:moims-dai-bounces@mailman.ccsds.org"><moims-dai-bounces@mailman.ccsds.org></a> <b>On Behalf
Of </b>Hughes, John S (US 398B) via MOIMS-DAI<br>
<b>Sent:</b> Tuesday, October 6, 2020 10:11 AM<br>
<b>To:</b> MOIMS-Data Archive Interoperability
<a class="moz-txt-link-rfc2396E" href="mailto:moims-dai@mailman.ccsds.org"><moims-dai@mailman.ccsds.org></a><br>
<b>Cc:</b> Hughes, John S (US 398B)
<a class="moz-txt-link-rfc2396E" href="mailto:john.s.hughes@jpl.nasa.gov"><john.s.hughes@jpl.nasa.gov></a><br>
<b>Subject:</b> Re: [Moims-dai] Component Diagram and
Updated Book<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi all,<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">Attached please
find the latest version of the book in both .doc and .pdf
formats.<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">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Steve<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"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Hughes, John S (US 398B)
<<a href="mailto:john.s.hughes@jpl.nasa.gov"
moz-do-not-send="true">john.s.hughes@jpl.nasa.gov</a>>
<br>
<b>Sent:</b> Monday, October 5, 2020 1:45 PM<br>
<b>To:</b> MOIMS-Data Archive Interoperability <<a
href="mailto:moims-dai@mailman.ccsds.org"
moz-do-not-send="true">moims-dai@mailman.ccsds.org</a>><br>
<b>Cc:</b> Hughes, John S (US 398B) <<a
href="mailto:john.s.hughes@jpl.nasa.gov"
moz-do-not-send="true">john.s.hughes@jpl.nasa.gov</a>><br>
<b>Subject:</b> FW: Component Diagram and Updated Book<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi all,<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">David mentioned
that he will not be able to attend tomorrow’s meeting of the
MOIMS Data Archive Interoperability group and asked that we
continue discussion of the OAIS-IF. <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">In preparation,
attached are the latest Component diagrams and an updated
version of the book. To help focus the discussion I like to
review the set of elements to determine whether we have the
minimal set needed. <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">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Steve</span><o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
MOIMS-DAI mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MOIMS-DAI@mailman.ccsds.org">MOIMS-DAI@mailman.ccsds.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai</a>
</pre>
</blockquote>
<div class="moz-signature">-- <br>
<img src="cid:part4.884BCD53.F2685ED2@comcast.net" border="0"></div>
</body>
</html>