<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">Hi all</div><div dir="auto"><br></div><div dir="auto">I can join the call at the start for a short while to check on OAIS but then I will drop out because I've had to take my wife to the physio.</div><div dir="auto"><br></div><div dir="auto">David</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000" dir="auto"><!-- originalMessage --><div>-------- Original message --------</div><div>From: kearneysolutions@gmail.com </div><div>Date: 24/09/2019 14:53 (GMT+00:00) </div><div>To: 'MOIMS-Data Archive Interoperability' <moims-dai@mailman.ccsds.org> </div><div>Cc: "'Hughes, John S (US 398B)'" <john.s.hughes@jpl.nasa.gov> </div><div>Subject: Re: [Moims-dai] MOIMS DAI - OAIS Interoperability Framework - Notes and Comments - Tuesday 9/17/19 </div><div><br></div></div><div class="WordSection1"><p class="MsoNormal">*<b>Really</b>* great writeup, Steve. I have the feeling this needs to be captured somewhere besides an email, but I don’t know where. Maybe “development notes” in the ADD? <o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Only one comment… <o:p></o:p></p><p class="MsoNormal"><span style="color:#1F497D">3.a.i. What basic protocol(s) are required?<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">That should be answered by finding plug-ins that are downloadable from well-known resources. Once he has the plugin, that should also resolve ii, iii, and iv. <o:p></o:p></span></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>Hughes, John S (US 398B) via MOIMS-DAI<br><b>Sent:</b> Saturday, September 21, 2019 11:36 AM<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] MOIMS DAI - OAIS Interoperability Framework - Notes and Comments - Tuesday 9/17/19<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">Here are some notes and a brief summary of the discussion items from our Tuesday 9/17/19 teleconference. Please feel free to comment and correct as necessary.<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<o:p></o:p></span></p><p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p><ol style="margin-top:0in" start="1" type="1"><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo3">Introduction and Scope – The document “Draft introductory statements for OAIS Interoperability Framework standard” written by David Giaretta 20190726, was accepted as a succinct statement of scope for the OAIS-IF Blue Book. Mike Kearney also noted that the draft Blue Book’s existing “Introduction and Scope” section contains the standard “boiler plate” for CCDSD documents. It was decided that David’s focus on Interfaces and Services would guide further development of the Blue Book and over time it will be integrated into the existing “Introduction and Scope” section of the Blue Book.<o:p></o:p></li></ol><p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p><ol style="margin-top:0in" start="2" type="1"><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo3">Accessing “Descriptive Information” from an OAIS – A question was posed as to how a Consumer (possibly another OAIS) obtains information from an OAIS about its holdings, primarily the AIPs it manages. For example, how would Archive B get the <Descriptive Information> for the AIPs in Archive B. This led to a number of discussion items.<o:p></o:p></li></ol><p class="MsoListParagraph"><span style="color:#1F497D"><o:p> </o:p></span></p><ol style="margin-top:0in" start="2" type="1"><ol style="margin-top:0in" start="1" type="a"><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level2 lfo3">The search/access component of the OAIS-IF must be limited to the most general level. Details including search protocols, query languages, etc are too varied and complex to be addressed now.<o:p></o:p></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level2 lfo3">However the OAIS Information Model (IM) must be known or be made accessible for potential Consumers to discover the “names” of the “items” in the archive that are accessible.<o:p></o:p></li></ol></ol><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>i.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">By definition the OAIS-RM IM provides the most basic named items. (e.g., Information_Package, Information Object, Provenance_Information, etc.)<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>ii.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">For a domain specific OAIS, a mechanism should be available for accessing domain specific extensions to the IM. (e.g., the PDS4 Product_Observational and Product_Context.)<o:p></o:p></span></p><ol style="margin-top:0in" start="2" type="1"><ol style="margin-top:0in" start="3" type="a"><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level2 lfo3">All information distributed out of the OAIS is distributed as an Information Package.<o:p></o:p></li></ol></ol><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>i.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">Are all Information Packages distributed from an OAIS considered to be DIPs?<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>ii.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">The consumer must have access to Representation Information for each Information Package.<o:p></o:p></span></p><ol style="margin-top:0in" start="2" type="1"><ol style="margin-top:0in" start="4" type="a"><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level2 lfo3">What can be the contents of a distributed Information Package?<o:p></o:p></li></ol></ol><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>i.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">Ideally there should be no limit on the type of information that can be included in a distributed Information Package.<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>ii.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">By definition the content may be any or a derivation of any AIP(s) in the OAIS.<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>iii.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">Descriptive Information used to support the finding, ordering, and retrieving of OAIS information holdings should be made available.<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>iv.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">Finding Aids should be made available. – If the Finding Aid is a process then it could be distributed as serialized code)<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>v.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">…<o:p></o:p></span></p><ol style="margin-top:0in" start="2" type="1"><ol style="margin-top:0in" start="5" type="a"><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level2 lfo3">This leads to the question, what are the OAIS-IM class(es) and method(s) that are responsible for Information Object management, for example Description Information?<o:p></o:p></li></ol></ol><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>i.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">In other words how are Information Objects that are not components of an AIP managed? <o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>ii.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">How are these Information Object accessed by Consumers?<o:p></o:p></span></p><ol style="margin-top:0in" start="2" type="1"><ol style="margin-top:0in" start="6" type="a"><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level2 lfo3">Since all AIPs (Information Objects) need to be registered, some type of Information Object registry should exist.<o:p></o:p></li></ol></ol><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>i.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">An Information Object registry seems implicit in the definition of the Data Management functional entity.<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in"><span style="color:#1F497D"><o:p> </o:p></span></p><ol style="margin-top:0in" start="3" type="1"><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo3">A Vision<o:p></o:p></li><ol style="margin-top:0in" start="1" type="a"><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level2 lfo3">Assume that there exists a Consumer that has very limited knowledge about an archive other than it conforms at some level to the OAIS-RM and has a very basic access/retrieval protocol.<o:p></o:p></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level2 lfo3">The Consumer should be able to request a series of Information Objects from the archive and “bootstrap” themselves up to a level where they have sufficient knowledge to effectively interact with the archive.<o:p></o:p></li></ol></ol><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>i.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">What basic protocol(s) are required?<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>ii.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">The OAIS IM class names and definitions need to be readily accessible. <o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>iii.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">How does the Consumer access the discipline extensions to the OAIS IM (class names and definitions)?<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo3"><!--[if !supportLists]--><span style="color:#1F497D"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman""> </span>iv.<span style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span style="color:#1F497D">How does the Consumer access the abstraction layer (class methods)?<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:1.0in"><span style="color:#1F497D"><o:p> </o:p></span></p></div></body></html>