<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:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>For completeness here is a copy of the email I sent to Mike commenting on his diagrams.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>------------------<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Hi Mike<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Nice detailed diagrams – we certainly need this level of detail.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>What I meant about adapters was that, as I wrote in the GB, the adapter surely must depends strongly on the software it is connected to, and is independent on what is at the other end of the network. Hence the Consumer (not necessarily Designated Community of the archive being communicated with) needs to obtain an adapter for its specific s/w. In the GB I gave an example of a pretty generic adapter for a type of archive. The OAIS-IF may talk to a registry which keeps copies of adapters for specific client software, but we would need to discuss that). So the OAIS-IF may know about some pre-prepared or generic adapters, but it would not be reasonable for the archive to have a whole set of adapters for everyone.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Also the basic communication between archive and consumer (to use specific names for the two ends of the communication) will need some “out of band” communication i.e. not specified by the standard OR we say that it is, for example specified in the standard as a specific REST request i.e. we say that one needs HTTP on Port 80 to set up the communications.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>My only other point is that there needs to be some iteration about RepInfo until either the consumer has enough – which may pull RepInfo from other registries of RepInfo – or else one gives up i.e. someone needs to “Research/Develop more RepInfo for data set X”, as you show in the diagram, but that must be for the Consumer side – you show it for the Provider. <o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I hope that helps.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>However, I I mentioned, things will be clearer if/when we start implementations, as long as we recognise what our implicit assumptions are. <o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>..David<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> MOIMS-DAI <moims-dai-bounces@mailman.ccsds.org> <b>On Behalf Of </b>Hughes, John S (US 398B) via MOIMS-DAI<br><b>Sent:</b> 15 June 2021 12:27<br><b>To:</b> MOIMS-Data Archive Interoperability <moims-dai@mailman.ccsds.org><br><b>Cc:</b> Hughes, John S (US 398B) <john.s.hughes@jpl.nasa.gov><br><b>Subject:</b> [Moims-dai] FW: [EXTERNAL] Interaction pattern discussion<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US>Hi all,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Attached please find some Interaction charts draw by Mike as part of an offline discussion. We can discuss these today.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Steve<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> <a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a> <<a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a>> <br><b>Sent:</b> Tuesday, June 8, 2021 12:14 PM<br><b>To:</b> <a href="mailto:david@giaretta.org">david@giaretta.org</a>; Hughes, John S (US 398B) <<a href="mailto:john.s.hughes@jpl.nasa.gov">john.s.hughes@jpl.nasa.gov</a>>; John Garrett <<a href="mailto:garrett@his.com">garrett@his.com</a>><br><b>Subject:</b> [EXTERNAL] Interaction pattern discussion<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Steve: Here is my non-programmer writeup explaining the interaction patterns, in layman’s language, that I volunteered to send you today. Some of these were not addressed in your UML tool interaction pattern graphics, and maybe aren’t needed or desired. But they just seem to be the dialog that we discussed. Note that I started with the example that the adapter was not provided by the archive, but rather another source in the designated community. A subset (the trivial example) would be where that source is actually in the archive. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Also, I separated a discovery phase from a data exchange phase, and even separated the data exchange phase into two examples… consumer and provider. You can keep or reject any of this. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>After I did this, I realized that I could have left the programmer calls over the arrows like you had (except I’m not capable of writing them) and had my “layman’s language” explanation of each transaction off to one side in a “notes” column. I think a lot of the discussion today was people not understanding the labels on each transaction arrow, and it would be less ambiguous to add notes off to the side like my (occasionally tongue-in-cheek) transaction labels. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>David, we couldn’t really figure out what you meant by the adapters were between my concept and Steve’s concept. So these charts may have the same problem for you that you briefly mentioned before. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#002060'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Mike Kearney<span style='color:#002060'><o:p></o:p></span></span></p><p class=MsoNormal><span lang=EN-US style='color:#002060'>Huntsville, Alabama, USA <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div></body></html>