<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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
mso-fareast-language:EN-GB;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@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=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Thanks Mario<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'>Some of us have looked at these and we are trying to ensure some level of consistency – we do not wish to re-invent the wheel! The extra level of complication which we must address is to handle the OAIS Information Model and ensuring the exchanged objects are understandable/usable.<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 seem to remember that SM&C produced some software. Do you know where that may be found?<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'>Regards<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><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>Mario.Merri@esa.int<br><b>Sent:</b> 15 June 2021 13:52<br><b>To:</b> MOIMS-Data Archive Interoperability <moims-dai@mailman.ccsds.org><br><b>Cc:</b> Duhaze Marc <Marc.Duhaze@cnes.fr><br><b>Subject:</b> Re: [Moims-dai] FW: [EXTERNAL] Interaction pattern discussion<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Dear all,</span> <br><br><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>since I see discussion related to interaction patterns, I invite you, if not done already, to consult the SM&C WG and in particular the MAL that has identified a set of generic Interaction Patterns. It would be very good to have the maximum synergy across WGs.</span> <br><br><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Many thanks,</span> <br><br><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>__Mario</span> <br><br><br><br><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F'>From: </span><span style='font-size:9.0pt;font-family:"Arial",sans-serif'><<a href="mailto:david@giaretta.org">david@giaretta.org</a>></span> <br><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F'>To: </span><span style='font-size:9.0pt;font-family:"Arial",sans-serif'>"'MOIMS-Data Archive Interoperability'" <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>></span> <br><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F'>Date: </span><span style='font-size:9.0pt;font-family:"Arial",sans-serif'>15/06/2021 13:37</span> <br><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F'>Subject: </span><span style='font-size:9.0pt;font-family:"Arial",sans-serif'>Re: [Moims-dai] FW: [EXTERNAL] Interaction pattern discussion</span> <br><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F'>Sent by: </span><span style='font-size:9.0pt;font-family:"Arial",sans-serif'>"MOIMS-DAI" <<a href="mailto:moims-dai-bounces@mailman.ccsds.org">moims-dai-bounces@mailman.ccsds.org</a>></span> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><p style='margin:0cm'>For completeness here is a copy of the email I sent to Mike commenting on his diagrams.<o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>------------------<o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>Hi Mike<o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>Nice detailed diagrams – we certainly need this level of detail.<o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>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></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>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></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>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></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>I hope that helps.<o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>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></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>..David<o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'><b>From:</b> MOIMS-DAI <<a 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<b><br>Sent:</b> 15 June 2021 12:27<b><br>To:</b> MOIMS-Data Archive Interoperability <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>><b><br>Cc:</b> Hughes, John S (US 398B) <<a href="mailto:john.s.hughes@jpl.nasa.gov">john.s.hughes@jpl.nasa.gov</a>><b><br>Subject:</b> [Moims-dai] FW: [EXTERNAL] Interaction pattern discussion<o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>Hi all,<o:p></o:p></p><p style='margin:0cm'>Attached please find some Interaction charts draw by Mike as part of an offline discussion. We can discuss these today.<o:p></o:p></p><p style='margin:0cm'>Thanks,<o:p></o:p></p><p style='margin:0cm'>Steve<o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'><b>From:</b> <a href="mailto:kearneysolutions@gmail.com"><span style='color:#0082BF'>kearneysolutions@gmail.com</span></a> <<a href="mailto:kearneysolutions@gmail.com"><span style='color:#0082BF'>kearneysolutions@gmail.com</span></a>> <b><br>Sent:</b> Tuesday, June 8, 2021 12:14 PM<b><br>To:</b> <a href="mailto:david@giaretta.org"><span style='color:#0082BF'>david@giaretta.org</span></a>; Hughes, John S (US 398B) <<a href="mailto:john.s.hughes@jpl.nasa.gov"><span style='color:#0082BF'>john.s.hughes@jpl.nasa.gov</span></a>>; John Garrett <<a href="mailto:garrett@his.com"><span style='color:#0082BF'>garrett@his.com</span></a>><b><br>Subject:</b> [EXTERNAL] Interaction pattern discussion<o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>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></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>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></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>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></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'>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></p><p style='margin:0cm'> <o:p></o:p></p><p style='margin:0cm'><span style='color:#002060'> -=- Mike</span><o:p></o:p></p><p style='margin:0cm'><span style='color:#002060'> </span><o:p></o:p></p><p style='margin:0cm'>Mike Kearney<o:p></o:p></p><p style='margin:0cm'><span style='color:#002060'>Huntsville, Alabama, USA </span><o:p></o:p></p><p style='margin:0cm'> <o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><br><tt><span style='font-size:10.0pt'>_______________________________________________</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>MOIMS-DAI mailing list</tt><br><tt><a href="mailto:MOIMS-DAI@mailman.ccsds.org">MOIMS-DAI@mailman.ccsds.org</a></tt><br></span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai"><tt><span style='font-size:10.0pt'>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><br></span><o:p></o:p></p><pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre><pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre><pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre><pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre></div></body></html>