<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=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
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.EmailStyle22
{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:1130131964;
mso-list-type:hybrid;
mso-list-template-ids:-1077891356 -1163228938 68419587 68419589 68419585 68419587 68419589 68419585 68419587 68419589;}
@list l0:level1
{mso-level-start-at:6;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.75in;
text-indent:-.25in;
font-family:Wingdings;}
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>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></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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></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 7:18 AM<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> 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><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><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='color:black;margin-left:.25in;mso-list:l0 level1 lfo2'> So an engineering archive might say “for my engineering data you need my engineering plugin and Autodesk’s Autocad plugin.” <o:p></o:p></li></ul><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="http://www.lotar-international.org/"><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'><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'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><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>From:</b> <a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a> [<a href="mailto:kearneysolutions@gmail.com">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">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></p></div></div><p class=MsoNormal><span lang=NO-BOK><o:p> </o:p></span></p><p class=MsoNormal>Hey, Dawei, glad to have your input in any form you can provide it. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Does that address your comment? <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>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">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></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Steve,<o:p></o:p></p><p class=MsoNormal> 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></p><p class=MsoNormal> 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></p><p class=MsoNormal> Thank you,<o:p></o:p></p><p class=MsoNormal> Dawei<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:black'>Dawei Lin, Ph.D.</span><span style='font-size:12.0pt;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'><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'><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'><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'><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'><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'><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'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'> <o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></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">moims-dai@mailman.ccsds.org</a>><br><b>Reply-To: </b>MOIMS-Data Archive Interoperability <<a href="mailto:moims-dai@mailman.ccsds.org">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">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></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><span style='color:#1F497D'>Hi all,</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>Attached is the latest version of a Component diagram that maps to Mike’s diagram. </span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>Steve</span><o:p></o:p></p></div></body></html>