<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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:99645608;
mso-list-type:hybrid;
mso-list-template-ids:455087634 852001722 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-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;
text-indent:-18.0pt;
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;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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;
text-indent:-18.0pt;
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;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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;
text-indent:-18.0pt;
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;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:152306557;
mso-list-type:hybrid;
mso-list-template-ids:499256440 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Hi Steve<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>My view is that as long as we say this is “OAIS” then the interoperability framework should reflect the OAIS Information Model (OAIS-IM). It could do other things but I believe that limiting ourselves to that will be useful enough. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>The clearest way to do that is to make it absolutely clear that the UML in the OAIS-IM is implemented. Therefore, for example, to get the Fixity Information (FI) of a particular Information Object (IO), <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>The route between the IO and FI would be<o:p></o:p></span></p><ul style='margin-top:0cm' type=disc><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Identify an Information Package (IP) that contains the IO <o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Use the IP which we have identified to identify the PDI (not that unless the IP is an AIP then there is no guarantee that it contains PDI)<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Use the PDI which we have identified to get to the FI (again we can only guarantee that the PDI gets us to the FI if we are dealing with an AIP).<o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>If the IO is being preserved then we can call it Content Information (CI). We can then reasonably say that the IP we want to deal with is an AIP, and hence must have PDI and FI etc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>If the framework interfaces allowed a user to perform those steps then I think everyone would agree that it reflects the OAIS-IM.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>In writing the above I realise that I am focussed on what a user can request from an archive. There is the other side of this which is “get me an IP, when I have it on my computer I can then open it up using the Packaging Information and extract the various components”. Clearly we need to be able to do that since in the end whatever the archive send us will be some kind of IP. Maybe in the book we need to make a distinction between (1) the requests we make to the archive and (2) what we can do with the IPs we get back.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Of course our interfaces may provide “convenience methods” such as – given some CI then get me the associated FI. Internally to the archive there may be a database that allows one to do that pretty directly, but that depends on the archive. If there is no such pre-prepared database then the archive would perform the steps mentioned above internally. Whichever way the archive does it is, from my point of view, irrelevant to the interfaces we are defining.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>So, in summary, I say that first and foremost our interface should clearly match the OAIS-IM UML. After we have done that then maybe we can think about what convenience methods we might add - although I would argue that we should not define any such convenience methods in the normative part of the book because that would be too open-ended, with no guidance from OAIS, and I would like the book to be completed as soon as possible.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Regards<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>..David<o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> MOIMS-DAI <moims-dai-bounces@mailman.ccsds.org> <b>On Behalf Of </b>Hughes, John S (398B) via MOIMS-DAI<br><b>Sent:</b> 13 June 2019 18:10<br><b>To:</b> MOIMS-Data Archive Interoperability <moims-dai@mailman.ccsds.org><br><b>Cc:</b> Hughes, John S (398B) <john.s.hughes@jpl.nasa.gov><br><b>Subject:</b> Re: [Moims-dai] [EXTERNAL] Re: Architecture Description<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Hi all,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This is the discussion I remember. Here is a use case.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>In the PDS4 Information Model we have the following hierarchy.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><ol style='margin-top:0cm' start=1 type=1><li class=MsoListParagraph style='color:#1F497D;margin-left:0cm;mso-list:l1 level1 lfo2'><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Bundle – A Bundle contains one or more Collections (E.g., a Bundle is typically a package containing a data product collection for a single instrument together with one or more collections of information necessary for using the data. ) The PDS4 bundle is effectively an OAIS Information_Package.<o:p></o:p></span></li><li class=MsoListParagraph style='color:#1F497D;margin-left:0cm;mso-list:l1 level1 lfo2'><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Collection -> A Collection contains one or more Data Products of a single type (e.g., all the raw images from the Viking Orbiter 1 and 2 cameras)<o:p></o:p></span></li><li class=MsoListParagraph style='color:#1F497D;margin-left:0cm;mso-list:l1 level1 lfo2'><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Data Products -> A Data Product containing data from a scientific observation. (e.g., one raw image from the Viking mission) The Raw image and its PDS4 label is effectively an OAIS Information_Object.<o:p></o:p></span></li></ol><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Viewing PDS4 as an OAIS, if a user finds and requests a Viking Image from the PDS they will typically receive an Information Object, i.e., the raw image (Data Object) and its Representation_Information. If the user then requests the Fixity Information for the raw image, under the OAIS-IF, how should system get the Data_Object’s Fixity_Information?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>According to the OAIS-IF Information Model the Fixity_Information is associated with the Preservation_Description_Information and the Preservation_Description_Information is associated with an Information_Package. This suggest that given the Viking Image Information_Object, the system will navigate through the Collection to the Bundle (an Information_Package), get the Preservation_Description_Information, get the Fixity_Information, and then locate and return the Fixity_Information specific to the Viking Image Information_Object.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Another view is that the system knows that the Viking Image Information_Object is Content_Information and directly gets the associated Fixity_Information.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thoughts?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Steve<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> MOIMS-DAI <<a href="mailto:moims-dai-bounces@mailman.ccsds.org">moims-dai-bounces@mailman.ccsds.org</a>> <b>On Behalf Of </b>david<br><b>Sent:</b> Wednesday, June 12, 2019 11:59 AM<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 (398B) <<a href="mailto:john.s.hughes@jpl.nasa.gov">john.s.hughes@jpl.nasa.gov</a>><br><b>Subject:</b> [EXTERNAL] Re: [Moims-dai] Architecture Description<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US>Yes, necessary, but not sufficient.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US>David<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div><div id="composer_signature"><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:#575757'>Sent from my Samsung Galaxy smartphone.<o:p></o:p></span></p></div></div><div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-US style='color:black'>-------- Original message --------<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='color:black'>From: Mark Conrad <<a href="mailto:mark.conrad@nara.gov">mark.conrad@nara.gov</a>> <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='color:black'>Date: 12/06/2019 19:15 (GMT+00:00) <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='color:black'>To: MOIMS-Data Archive Interoperability <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>> <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='color:black'>Cc: "Hughes, John S (398B)" <<a href="mailto:john.s.hughes@jpl.nasa.gov">john.s.hughes@jpl.nasa.gov</a>> <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='color:black'>Subject: Re: [Moims-dai] Architecture Description <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='color:black'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal><span lang=EN-US>"Preservation Description Information (PDI): The information, which along with Representation Information, is necessary for adequate preservation of the <b><i>Content Data Object</i></b>"<br clear=all><o:p></o:p></span></p><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div><div><p class=MsoNormal><span lang=EN-US>On Wed, Jun 12, 2019 at 1:38 PM David Giaretta <<a href="mailto:david@giaretta.org">david@giaretta.org</a>> wrote:<o:p></o:p></span></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>In OAIS terms PDI may be part of any Information Package. If the Information Package is an AIP then by implication the Information Object it will probably be Content Information.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>..David<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span lang=EN-US>From:</span></b><span lang=EN-US> 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>Mark Conrad<br><b>Sent:</b> 12 June 2019 17:51<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 (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] Architecture Description</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>" <span style='color:black'>I cannot understand why Content_Information (a sub-type of Information_Object) shows methods get/putPreservationDescriptionInformation. That would normally indicate that these are additional methods in addition to those which Information_Object has – but why?</span> "<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Because PDI does not apply to all Information_Objects - only Content_Information.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <br clear=all><o:p></o:p></p><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Mark Conrad<br>NARA Information Services<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>Systems Engineering Division (IT)<br>The National Archives and Records Administration<br>Erma Ora Byrd Conference and Learning Center<br>Building 494, Room 225<br>610 State Route 956<br>Rocket Center, WV 26726<br><br>Phone: 304-726-7820<br>Fax: 304-726-7802<br>Email: <a href="mailto:mark.conrad@nara.gov" target="_blank">mark.conrad@nara.gov</a> <o:p></o:p></p></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Tue, Jun 11, 2019 at 9:17 AM David Giaretta <<a href="mailto:david@giaretta.org" target="_blank">david@giaretta.org</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi Steve<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I can understand why get/setDataObject and get/putRepresentationInformation are methods in Information_Object but I don’t understand why get/putInformationObjectMetadata is there. Also don’t understand the difference between get/setPID and get/putIdentificationInformation. Also what is the difference between put and set?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I cannot understand why Content_Information (a sub-type of Information_Object) shows methods get/putPreservationDescriptionInformation. That would normally indicate that these are additional methods in addition to those which Information_Object has – but why?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Is there are mix-up between Information_Object and Information_Package?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I suspect that part of my confusion arises from using the ontology rather than a UML tool to create the diagrams etc. but that would not explain my questions/comments above.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>..David<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span lang=EN-US>From:</span></b><span lang=EN-US> 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>Hughes, John S (398B) via MOIMS-DAI<br><b>Sent:</b> 11 June 2019 03:16<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 (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] Architecture Description</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='color:#1F497D'>Hi all,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='color:#1F497D'>Attached please find the Model Specification Document (html format) and two diagrams with a few updates to some core classes. In particular the DPI get/put methods have been moved to the Content_Information class as per recent discussions.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='color:#1F497D'>Thanks,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='color:#1F497D'>Steve</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='color:#1F497D'> </span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>_______________________________________________<br>MOIMS-DAI mailing list<br><a href="mailto:MOIMS-DAI@mailman.ccsds.org" target="_blank">MOIMS-DAI@mailman.ccsds.org</a><br><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai" target="_blank">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai</a><o:p></o:p></p></blockquote></div></div></div><p class=MsoNormal><span lang=EN-US>_______________________________________________<br>MOIMS-DAI mailing list<br><a href="mailto:MOIMS-DAI@mailman.ccsds.org" target="_blank">MOIMS-DAI@mailman.ccsds.org</a><br><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai" target="_blank">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai</a><o:p></o:p></span></p></blockquote></div></div></body></html>