<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=us-ascii"><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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I had a few other things I wanted to say/document, which we can discuss on email or at a future telecon. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We had a discussion about whether the interoperability framework includes *<b>only</b>* functions in the OAIS Information Model, or *<b>also</b>* things that are outside the information model but within the OAIS Reference model. Reports on SIP (or AIP?) contents for virus scanning or CRCs were examples. We tried to explain that away as being inside provenance, hence handled at the user interface as provenance, hence within the information model. But if it is not handled as provenance, i.e. if it is not in the information model, then we’ve got a potential “hole” in the interoperability architecture if it is not included as a specific function in the architecture. Similarly, we discussed that there may be things external to the AIP, yet having a relationship to the AIP, such as logs. Logs (we agreed, I think) are not included in the AIP, and are not in the information model. Do they surface at the interoperability interface? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I may have misunderstood, but I think this discussion of inside/outside of the info model or interoperability framework is an open question for future discussion. Steve, if you think this was resolved, let us know. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It might be interesting to see how SM&C handled this. Do they have “reports” as part of their user interface? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>One step further… I think if those reports (submission reports, virus scan reports, logs, etc.) are human-readable PDF reports, then they don’t need to be part of the interoperability interface (I know… there may need to be agreement on human language, but I think that can be handled completely outside of the interoperability architecture). If those reports are machine readable software constructs sent to a user interface application (like an application display or other communications construct) then they <b><i>do</i></b> need to be part of the interoperability interface. I think John commented (and agreed, I think) on this point when he mentioned something like “only communication protocols”. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We kept using the “user interface” (producer/consumer interface) as the example of where salient interoperability features would surface, and hence what needed to be defined in the interoperability framework architecture. However, there are more interfaces… (1) between the user interface and the abstraction layer, (2) between the abstraction layer and the plugin/binding, (3) between the plugin/binding and the archive. We need those defined in the architecture as well, because this is a layered/modular interoperability architecture. Therefore, features that affect interoperability at any of those interfaces need to be described in Steve’s architecture model and architecture document. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Terry brought up (again, I think) the question of how interfaces between archives are handled. In the past, I thought we agreed that archive-to-archive interfaces would utilize the same interfaces as producers and consumers. An archive sending data to another archive uses the “producer interface” of the receiving archive, and sends SIPs. And a submission agreement is sent in advance. I suppose that if the submission agreement accommodates it, the sending archive could alternatively send DIPs. In any case, no “special” interface was needed for transactions between archives. An archive viewed another archive as just another producer or consumer. Steve, this question has come up several times, so if this is our approach, it should probably be documented in the introduction of the architecture document. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Those are my thoughts after today’s discussion. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><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><p class=MsoNormal><o:p> </o:p></p></div></body></html>