<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;}
span.EmailStyle20
{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: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>My thought is that all the functions (language, capabilities, underlying protocols) for any given archive should be “bundled” into a single plug-in (binding/API/protocol) that a user downloads for access to any given archive. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I did have a notion that perhaps certain vendors (Adobe for PDF, Autodesk for Autocad, IIPC for HTML, etc.) could provide plugins that are for certain common data formats so that the plug-in provider (archive or designated community) doesn’t necessarily have to add common file format sensitivity to their plugin for their archive. In that case, maybe multiple plugins would be needed to access an archive that has unique formats plus those common formats. This concept is also in the PPT charts that we’ve been using since the beginning. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>But other than that, I don’t think we want multiple plugins for a single archive, if possible. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As we discussed, the binding should be able to provide access (Level 0) to a different designated community’s archive than he has without the binding. But it doesn’t necessarily translate/convert to formats (Level 1-5) used by those external to the archive (public, other designated communities, etc.). <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I switched the lowest from Level 1 to Level 0 when Steve did, but maybe we should stick with Level 1 for Access, just in case we find something else later that is even more primitive than just access. <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 <moims-dai-bounces@mailman.ccsds.org> <b>On Behalf Of </b>garrett@his.com<br><b>Sent:</b> Tuesday, May 12, 2020 1:11 AM<br><b>To:</b> 'MOIMS-Data Archive Interoperability' <moims-dai@mailman.ccsds.org><br><b>Subject:</b> Re: [Moims-dai] Component Diagram - Consumer and Producer Application Update<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Are there different types of “bindings” we need different terms for?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“Binding” of the abstract functions/information to the implementation programming language/DB/formats<o:p></o:p></p><p class=MsoNormal>“Binding” of the abstract functions/information to the actual archive/producer/consumer capabilities<o:p></o:p></p><p class=MsoNormal>“Binding” of the abstract/actual functions/information to the underlying communication protocols<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think we may need to look at all of these aspects.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Maybe we need some 3D views to include all of them.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>May there be peace in your life,<o:p></o:p></p><p class=MsoNormal>-JOhn <o:p></o:p></p><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 href="mailto:moims-dai-bounces@mailman.ccsds.org">moims-dai-bounces@mailman.ccsds.org</a>> <b>On Behalf Of </b><a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a><br><b>Sent:</b> Monday, May 11, 2020 7:20 PM<br><b>To:</b> 'MOIMS-Data Archive Interoperability' <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>><br><b>Cc:</b> 'Hughes, John S (US 398B)' <<a href="mailto:john.s.hughes@jpl.nasa.gov">john.s.hughes@jpl.nasa.gov</a>><br><b>Subject:</b> Re: [Moims-dai] Component Diagram - Consumer and Producer Application Update<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Looks good, Steve, it’s getting there. Still nothing in the binding, though. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The “Archive Interface” functions; are those in the archive systems, or in the user systems. They sort of look to me like they could be in the user systems, hence the “Archive interface” would be part of the binding. <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 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> Monday, May 11, 2020 6:10 PM<br><b>To:</b> MOIMS-Data Archive Interoperability <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>><br><b>Cc:</b> Hughes, John S (US 398B) <<a href="mailto:john.s.hughes@jpl.nasa.gov">john.s.hughes@jpl.nasa.gov</a>><br><b>Subject:</b> [Moims-dai] Component Diagram - Consumer and Producer Application Update<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 is the latest version of a Component diagram that maps to Mike’s diagram. The key changes include adding Consumer and Producer applications to the application layer.<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></body></html>