<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle220
{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;}
/* List Definitions */
@list l0
{mso-list-id:1334839383;
mso-list-template-ids:1387301840;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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>Actually, I am quite the minor player, just trying to find examples of plugins that everyone likes. The major players are, of course, David and John Garrett, our chairs, and (John) Steve Hughes, our architecture lead. They would be the ones to take the lead on the OAIS topics you suggested. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>David, John, Steve, thoughts? <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> Kjell Bengtsson <Kjell.Bengtsson@jotne.com> <br><b>Sent:</b> Wednesday, May 20, 2020 1:30 PM<br><b>To:</b> kearneysolutions@gmail.com; 'MOIMS-Data Archive Interoperability' <moims-dai@mailman.ccsds.org><br><b>Cc:</b> 'Lin, Dawei (NIH/NIAID) [E]' <dawei.lin@nih.gov>; 'Hughes, John S (US 398B)' <john.s.hughes@jpl.nasa.gov><br><b>Subject:</b> SV: [Moims-dai] Component Diagram - Consumer and Producer Application Update<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>Hi Mike, </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>One of our PhD students, Remi Lanza, has been working with LOTAR for a couple of years. </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>One of his papers (out of 3) is available here: <a href="https://ntnuopen.ntnu.no/ntnu-xmlui/bitstream/handle/11250/2585839/Relating%2bstructural%2btest%2band%2bFEA%2bdata%2bwith%2bSTEP%2bAP209_official.pdf?sequence=1&isAllowed=y">https://ntnuopen.ntnu.no/ntnu-xmlui/bitstream/handle/11250/2585839/Relating%2bstructural%2btest%2band%2bFEA%2bdata%2bwith%2bSTEP%2bAP209_official.pdf?sequence=1&isAllowed=y</a></span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'><br>We have currently 3 EU projects (Arrowhead Tools, Kyklos 4.0, Change2Twin) and some ESA projects, that has strong interests in archiving. One ESA example here: <a href="https://myemail.constantcontact.com/ESA-Focus-on-ISO-Standards.html?soid=1103697758295&aid=RbtmVtUE7fo" title="https://myemail.constantcontact.com/ESA-Focus-on-ISO-Standards.html?soid=1103697758295&aid=RbtmVtUE7fo
Ctrl+Klikk for å følge kobling">https://myemail.constantcontact.com/ESA-Focus-on-ISO-Standards.html?soid=1103697758295&aid=RbtmVtUE7fo</a></span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>Maybe Remi could have a look into your ideas and see what could be done? </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>I would propose a web meeting with you, Remi, Jochen Haenisch and me to discover a possible way forward, </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>Agenda Topics could be; </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>1. OAIS updates on architectures (find the way in the models/processes)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>2. OAIS Conops for engineering data (undestanding other use-cases, and a deep dive into the Engineering informationn datastore)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>3. Jotne to present ISO 10303/Open BIM capabilities</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>4. What could be a joint contribution and planning of such STEP/BIM plug-in efforts? </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>5. AOB</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>What do you think? </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>We are closed rest of the week due to public holidays, so a time slot next week or later will work. </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana",sans-serif;color:black'>Best regards, Kjell </span><span style='color:black'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif;color:black'><o:p> </o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:12.0pt;font-family:"Times New Roman",serif;color:black'><hr size=2 width="100%" align=center></span></div><div id=divRpF71963><p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black'>Fra:</span></b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black'> <a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a> [kearneysolutions@gmail.com]<br><b>Sendt:</b> 20. mai 2020 19:59<br><b>Til:</b> Kjell Bengtsson; 'MOIMS-Data Archive Interoperability'<br><b>Kopi:</b> 'Lin, Dawei (NIH/NIAID) [E]'; 'Hughes, John S (US 398B)'<br><b>Emne:</b> RE: [Moims-dai] Component Diagram - Consumer and Producer Application Update</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif;color:black'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='color:black'>That was just intended as an example, albeit maybe a poor example. Several DAI folks, me included, had telecons with LOTAR folks (at their request) in March. If memory serves me right, in the OAIS-IF overview, I even suggested that LOTAR might arrange for the development of an “enterprise data” plug-in, for the data types that LOTAR is concerned with. Didn’t get much reaction from that, and went on to other preservation topics. <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>So… I should instead use an example of an ISO 10303 plug-in? Is there a candidate organization that might develop that for the community? <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><div><p class=MsoNormal><span style='color:#002060'> -=- Mike </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Mike Kearney</span><span style='color:#002060'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA </span><span style='color:black'><o:p></o:p></span></p></div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='color:black'>From:</span></b><span style='color:black'> Kjell Bengtsson <<a href="mailto:Kjell.Bengtsson@jotne.com">Kjell.Bengtsson@jotne.com</a>> <br><b>Sent:</b> Wednesday, May 20, 2020 7:18 AM<br><b>To:</b> <a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a>; 'MOIMS-Data Archive Interoperability' <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>><br><b>Cc:</b> 'Lin, Dawei (NIH/NIAID) [E]' <<a href="mailto:dawei.lin@nih.gov">dawei.lin@nih.gov</a>>; '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></span></p></div></div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Hi Mike, <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:10.0pt;font-family:Symbol;color:black'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:black'> So an engineering archive might say “for my engineering data you need my engineering plugin and Autodesk’s Autocad plugin.” <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.25in'><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Probably not. Most people in the Engineering Community is looking for a no-vendor lock-in of data. Today more than 80% of all CAD data exchange is using ISO 10303 (STEP) and similar for the Building Industry uses the OpemBIM/IFC ISO standards. So any application with such read/write/validate capability (or call it plugin) should be able to open the ISO/STEP/BIM format. <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Most relevant for this discussion is to have a look at <a href="https://eu-west-1.protection.sophos.com?d=lotar-international.org&u=aHR0cDovL3d3dy5sb3Rhci1pbnRlcm5hdGlvbmFsLm9yZy8=&e=a2plbGwuYmVuZ3Rzc29uQGpvdG5lLmNvbQ==&h=299a4006d4ae41b8b25fbcb4e9ca1b19&t=RURQOU5QSGRDRUg5aUI5T2xHQnpBclIzQTNobVBTUEhYdFk2Q2dGZmZmaz0=" target="_blank"><span style='color:black'>LOTAR International</span></a> for archiving of Engineering data, using the ISO 10303 (CAD/CAE/TEST/PLM/ILS/Sensor) ISO 16739 (BIM) standards for data exchange, sharing <i><u>and archiving.</u></i> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Currently, Jotne is tasked by the Norwegian National Archive to do a study for how to archive BIM/IFC data which since now is a law in Norway, “FOR-2017-12-19-2286”. <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Best regards, Kjell <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='color:black'>From:</span></b><span style='color:black'> <a href="mailto:kearneysolutions@gmail.com" target="_blank">kearneysolutions@gmail.com</a> [<a href="mailto:kearneysolutions@gmail.com" target="_blank">mailto:kearneysolutions@gmail.com</a>] <br><b>Sent:</b> tirsdag 19. mai 2020 17.17<br><b>To:</b> 'MOIMS-Data Archive Interoperability' <<a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">moims-dai@mailman.ccsds.org</a>><br><b>Cc:</b> 'Lin, Dawei (NIH/NIAID) [E]' <<a href="mailto:dawei.lin@nih.gov" target="_blank">dawei.lin@nih.gov</a>>; 'Hughes, John S (US 398B)' <<a href="mailto:john.s.hughes@jpl.nasa.gov" target="_blank">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></span></p></div></div><p class=MsoNormal><span lang=NO-BOK style='color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Hey, Dawei, glad to have your input in any form you can provide it. <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>In the architecture concept, we have plug-ins or bindings that are specific to each archive (Science, Engineering, DNA, Geology are just examples) or in some cases to each data format (PDF, HTML are just examples). If some archive wanted to have a “research” plug-in/binding that combined Science and Engineering, that would be perfectly OK. But it is up to the archive to define the scope of each plugin that is needed to access their archive. <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>The idea with some plugins being data formats rather than archive (designated community) specific was so that some commercial vendors can help the archive by publishing a plug-in for their complex software. Like Adobe might produce a PDF plugin, Autodesk might publish an Autocad plugin, etc. These would be supplemental to the main plugin needed for an archive. So an engineering archive might say “for my engineering data you need my engineering plugin and Autodesk’s Autocad plugin.” <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>We discussed your comment, and we think that Steve will change “Binding” on his diagram to “Binding Layer” and that will make it more clear that the box is not actually a binding, but a layer that can be composed of many types of bindings, with only a few examples shown. <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Does that address your comment? <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><div><p class=MsoNormal><span style='color:#002060'> -=- Mike </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Mike Kearney</span><span style='color:#002060'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA </span><span style='color:black'><o:p></o:p></span></p></div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='color:black'>From:</span></b><span style='color:black'> MOIMS-DAI <<a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">moims-dai-bounces@mailman.ccsds.org</a>> <b>On Behalf Of </b>Lin, Dawei (NIH/NIAID) [E] via MOIMS-DAI<br><b>Sent:</b> Monday, May 18, 2020 4:52 PM<br><b>To:</b> MOIMS-Data Archive Interoperability <<a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">moims-dai@mailman.ccsds.org</a>><br><b>Cc:</b> Lin, Dawei (NIH/NIAID) [E] <<a href="mailto:dawei.lin@nih.gov" target="_blank">dawei.lin@nih.gov</a>>; Hughes, John S (US 398B) <<a href="mailto:john.s.hughes@jpl.nasa.gov" target="_blank">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></span></p></div></div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Hi Steve, <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> Sorry that I have not been able to participate in the weekly calls because of a conflict of another regular call. <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> From the perspective of not knowing the context, I think that “research data” sounds more general than “scientific data” and “engineering data” in Component_Diagram_200518.jpg, which may be useful to describe a broad concept. Also, depending on the definition of “Science Data”, it may need the same implementation of “Native Archive” as the “Engineering Data” does. But again, I did not participate in a lot of discussions, so what I said is entirely off. <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> Thank you, <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> Dawei <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Dawei Lin, Ph.D.</span><span style='font-size:12.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Associate Director for Bioinformatics and Senior Advisor to the Director</span><span style='font-size:12.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Division of Allergy, Immunology, and Transplantation</span><span style='font-size:12.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>National Institute of Allergy and Infectious Diseases</span><span style='font-size:12.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>5601 Fisher’s Lane 7A70, MSC 9828</span><span style='font-size:12.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Rockville MD, 20852</span><span style='font-size:12.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Work phone: 240-627-3527</span><span style='font-size:12.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Cell Phone: 301-312-3986</span><span style='font-size:12.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>"Hughes, John S (US 398B) via MOIMS-DAI" <<a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">moims-dai@mailman.ccsds.org</a>><br><b>Reply-To: </b>MOIMS-Data Archive Interoperability <<a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">moims-dai@mailman.ccsds.org</a>><br><b>Date: </b>Monday, May 18, 2020 at 12:40 PM<br><b>To: </b>MOIMS-Data Archive Interoperability <<a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">moims-dai@mailman.ccsds.org</a>><br><b>Cc: </b>"Hughes, John S (US 398B)" <<a href="mailto:john.s.hughes@jpl.nasa.gov" target="_blank">john.s.hughes@jpl.nasa.gov</a>><br><b>Subject: </b>[Moims-dai] Component Diagram - Consumer and Producer Application Update </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'>Hi all,</span><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> </span><span style='color:black'> <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. </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> </span><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,</span><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Steve</span><span style='color:black'> <o:p></o:p></span></p></div></div></div></div></div></div></body></html>