<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Mark,</p>
    <p>Thanks for your clarification.  I think you've made a significant
      improvement by creating situational definitions for these three. 
      I hope we can form a consensus around them. <br>
    </p>
    <p>I was at first concerned about the expression 'traceable to' in
      Item 3. Because it better reflects the activity needed to create a
      DIP, I preferred the construction 'derived from' instead of
      'traceable to' but I'm willing to drop that quibble. I had thought
      the intention of 'traceable to' to be that a DIP would be required
      to have clear or open text identifying the detailed sources and
      methods that generated it's outputs(or payload or intended Content
      or PDI). That  might in some cases be a potential breach of
      privacy or security considerations.  I realize now that that was a
      misinterpretation. <br>
    </p>
    <p>Even if others might be lead down the same path, I'm not sure if
      we want to clarify this intention.   Internally, of course, the
      Archive would need to maintain traceability to the sources and
      (algorithms/processes?) used to create a particular DIP. But the
      DIP would need only to contain a unique (trans)action identifier,
      probably including a timestamp, which could be used by some
      authorized ("cleared") agent to perform the necessary traceback
      research should the need arise.  It leads to an interesting
      question of provenance, which, for the DIP would be a composition
      of all of the aforementioned sources and processes as collected
      under the action identifier even if only the action identifier
      would be available to the DIP recipient.<br>
    </p>
    <p>Terry<br>
    </p>
    <div class="moz-cite-prefix">On 2019-08-29 4:45 PM, Mark Conrad
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAB===Vw7yEStAAb5VnhqMYqvPPyA6R0LE_kZxe5gnFP6dJREaw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <p class="MsoNormal" style="margin:0in 0in
          8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">OAIS
          2012:</p>
        <p class="MsoNormal" style="margin:0in 0in
          8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">Information
          Package: A logical container composed of optional
          Content Information and optional associated Preservation
          Description
          Information. Associated with this Information Package is
          Packaging Information
          used to delimit and identify the Content Information and
          Package Description
          information used to facilitate searches for the Content
          Information.</p>
        <p class="MsoNormal" style="margin:0in 0in
          8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"> </p>
        <p class="MsoNormal" style="margin:0in 0in
          8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">Proposed
          replacement:</p>
        <p class="MsoNormal" style="margin:0in 0in
          8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">Information
          Package: A logical container used for one of
          three purposes:</p>
        <p class="gmail-MsoListParagraphCxSpFirst" style="margin:0in 0in
          0.0001pt
          0.5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">1.<span
style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"Times
            New Roman"">      
          </span>To transmit from the Producer to the OAIS information
          to be used in constructing or updating Content Information and
          Preservation
          Description Information. (Submission Information Package -
          SIP)</p>
        <p class="gmail-MsoListParagraphCxSpMiddle" style="margin:0in
          0in 0.0001pt
          0.5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">2.<span
style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"Times
            New Roman"">      
          </span>To manage and preserve Content Information and
          its associated Preservation Description Information. (Archival
          Information
          Package - AIP)</p>
        <p class="gmail-MsoListParagraphCxSpLast" style="margin:0in 0in
          8pt
          0.5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">3.<span
style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"Times
            New Roman"">      
          </span>To transmit from the OAIS to the Consumer
          information that is traceable to the Content Information
          and/or Preservation
          Description Information contained in one or more Archival
          Information Package.
          (Dissemination Information Package - DIP)</p>
        <p class="MsoNormal" style="margin:0in 0in
          8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">NOTE:
          There are different requirements/constraints that are
          applicable to each type of Information Package (i.e., SIP,
          AIP, and DIP). See
          the definition of each Information Package type and the
          discussion at Section
          4.2.2.</p>
        <p class="MsoNormal" style="margin:0in 0in
          8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><br>
        </p>
        <p class="MsoNormal" style="margin:0in 0in
          8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">Talk
          to you next Tuesday!</p>
        <div>
          <div dir="ltr" class="gmail_signature"
            data-smartmail="gmail_signature">
            <div dir="ltr">
              <div>
                <div dir="ltr">
                  <div>
                    <div dir="ltr">
                      <div>
                        <div dir="ltr">
                          <div>Mark Conrad<br>
                            NARA Information Services</div>
                          <div>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" moz-do-not-send="true">mark.conrad@nara.gov</a>
                            <br>
                            <br>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </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:part2.0DB6BF4D.0CFF58B1@comcast.net" border="0"></div>
  </body>
</html>