<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: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;
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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#993366;}
.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:280844938;
mso-list-template-ids:1694276758;}
@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;}
@list l1
{mso-list-id:486751467;
mso-list-type:hybrid;
mso-list-template-ids:1691647518 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l2
{mso-list-id:539821938;
mso-list-type:hybrid;
mso-list-template-ids:-1478446504 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l3
{mso-list-id:1521158621;
mso-list-template-ids:933109710;}
@list l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='color:#993366'>David: I went ahead and made the changes for the RepInfo IF’s book to Charts 1 and 2, but I wasn’t sure how to reflect it on Chart 3. I figure we should let these ideas percolate for awhile and then update Chart 3 and the “resources” chart from the EWA presentation. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>I also made the change to one Generic adapter (vs. separate User and Archive Generic Adapters) to Charts 1 and 2. But when I looked at Chart 3, it occurred to me that while User and Archive Generic Adapter specs could be in one book, they may be separate functions (sections) in that book. The Archive Generic adapter is combining things into one package and sending them out one port to the WAN. The User Generic adapter is taking things from the one WAN port and unpacking them to go to the user. Not sure this can be combined into one specification and used like a “mirror flip-flop” if you know what I mean. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>To expand; the “wavy red line” between the generic adapters and the specific adapters is one interface. The wavy red line between the generic adapters and the WAN is a different interface. In the user GA the flow is in one direction, and in the archive GA it’s in the opposite direction. I suppose there can be one executable specified with bi-directional interfaces. But is that the most efficient way to do it? If someone wanted to implement separate User and Archive GA’s should we preclude that? <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>Also, I’m not confident about showing PAIS and CAIS in the “flow” on chart 3. Are those procedures functions really in the flow? Perhaps it’s OK as is, because this really illustrates a flow of “applicability” rather than a flow of “data” (or maybe it’s a hybrid diagram showing both.) Alternatively, I could take PAIS and CAIS out of the flow, have them above the OAIS-IF flow and just have them “floating” below PAIMAS and CAIMAS. Not sure. Comments welcome. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>Bottom line… I didn’t update Chart 3 yet with these ideas. Update attached and also in the dropbox. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></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><span style='color:#993366'>Mike Kearney</span><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><span style='color:#993366'><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> kearneysolutions@gmail.com <kearneysolutions@gmail.com> <br><b>Sent:</b> Wednesday, April 27, 2022 7:57 AM<br><b>To:</b> david@giaretta.org<br><b>Subject:</b> RE: [Moims-dai] Doc Tree<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>All sounds good, David, I’ll work on it today. <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'>For the “RepInfo Information Interfaces” book, I suppose I just put it at the bottom left with the other RepInfo standards. Or, since we haven’t discussed it in the group, we should hold off until we discuss it? Or maybe until we’ve added it to our schedule, and we’re certain it’s a “go”? <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></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><span style='color:#1F497D'>Mike Kearney</span><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><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:david@giaretta.org">david@giaretta.org</a> <<a href="mailto:david@giaretta.org">david@giaretta.org</a>> <br><b>Sent:</b> Wednesday, April 27, 2022 4:08 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> <a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a><br><b>Subject:</b> RE: [Moims-dai] Doc Tree<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB>Hi Mike<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>A great improvement but just a couple of comments from the point of view of simplification and estimates of effort needed.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>I think the only change to the diagram is that we would just need one Generic Adapter book. The idea was that any system could act as an information source (archive) or sink (user) at various points e.g. an Archive needs to ingest information i.e. act as a sink. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>In terms of work needed - the first Specific Adapter book could be rather simple “fairly general” Specific Adapter which could be used quite widely for archives which currently just act essentially as file/web servers i.e. “File Server Specific Adapter”.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>My hope was that the Registry and the Switchboard could really be specialised, fairly simple archives which could be quite short, based on the “File Server Specific Adapter”.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>The thing we need to add would be how to deal with Representation Information in a realistic way – a “Representation Information Interfaces” book. In principle we could also create a book to cover other aspects of the Information Model in more detail than is currently in Steve’s diagrams e.g. interfaces for Provenance, Context, Fixity, Reference and Access Rights. These could be very minimal with appendices pointing at various published implementations e.g. OPM for Provenance. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I’ve been looking at some of the commercial and free archival systems which are out there, for example Archivematica and others. We would try to ensure that out interfaces can accommodate these, as well as home grown systems (PDS? etc).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Regards<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>..David<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><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> MOIMS-DAI <<a href="mailto:moims-dai-bounces@mailman.ccsds.org">moims-dai-bounces@mailman.ccsds.org</a>> <b>On Behalf Of </b>Mike Kearney via MOIMS-DAI<br><b>Sent:</b> 26 April 2022 22:53<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> <a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a><br><b>Subject:</b> [Moims-dai] Doc Tree<o:p></o:p></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal>I had the action after the telecon today to update the Doc Tree for the Green book, factoring in the new architecture. The Doc Tree <a href="https://www.dropbox.com/s/0wz029riy0e8cfi/2021-01-18%20OAIS-IF%20Document%20Tree.pptx?dl=0">version in the DropBox</a> was not quite up to date to the version that was in the Green Book, but that didn’t matter because we revamped all that anyway. David, you might check whether there is something on the Green Book version that you didn’t want to lose. Also, David, in the drop box is a file “<a href="https://www.dropbox.com/s/9ahnioc5duq72en/OAIS-IF-diagrams.pptx?dl=0">OAIS diagrams</a>” which also had these drawings and several others that are out-of-date. You might want to clean that up (just delete obsolete drawings) to avoid confusion. I recommend we keep these Doc Tree pictures in this separate Doc Tree document, because they’re important and get lost in the other miscellaneous drawings. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The original file in the Dropbox (link above) actually had three pages. Firstly, the “DAI WG Document Tree”, secondly the “Relationship of CCSDS DAI WG standards, and thirdly, the “Specific Standards to be Developed (the blocky diagram with the complicated keyholes). I updated the first two, and just deleted that third drawing as obsolete and too difficult to update to the new architecture. I added a new third page that is from the EWA presentation, “OAIS Architecture Concept – Functions,” that is the driving drawing that shows the current architecture. David, in the EWA presentation, there is also the “OAIS Architecture Concept – Resources” drawing that is the same block diagram with resource description. You might consider whether you want that in the green book, and in this PPT as well. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So, here’s what changed.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Chart 1: <o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l1 level1 lfo3'>John suggested adding the code to show “published, in-work, and future” documents. I copied it from chart 2 and added it to chart 1. It does clutter it up a bit, but if we need the legend on both charts 1 and 2, this is the best I could do. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l1 level1 lfo3'>For chart 1, all the blue books were redone, adapters added (IAW the new architecture), and the Archive Abstraction Layer (AAL) was deleted. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l1 level1 lfo3'>I deleted PAIP and CAIP from the first two drawings, as we discussed, until we’re more certain that we’re going to do those. Unless they’re needed in the new architecture, driven by needs of the adapters, I think we leave those out of our future plans. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l1 level1 lfo3'>I kept CAIS as a future document in CHART 2, but combined it with PAIS in Chart 1 for legibility. Also, it occurs to me that we might put CAIS in the same book as PAIS anyway. Future question when we address CAIS on our development schedule. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l1 level1 lfo3'>Put all the blue books directly under the ADD. With the AAL gone, it’s not clear that any of these books are subordinate to anything except the ADD. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l1 level1 lfo3'>As we discussed today, there may be only one generic adapter, but I split it into two for User and Archive just to match our architecture (Chart 3). We should discuss it and if we’re really targeting one generic adapter for use by both users (producers and consumers) and archives, I should change this to reflect that. A “Generic Adapters” Blue Book. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l1 level1 lfo3'>Steve, there are major implications with that. The ADD needs to “call into existence” all the Blue Books, including existing PAIS, EAST, DESDL, PVL and XFDU. Also the Switchboard and Registry. I imagine you’ll need help from David and John to put near-term placeholders and long-term content for them in the ADD. <o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Chart 2: <o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l2 level1 lfo6'>Note that this is an old chart that David initiated to show the flow between Producers, Archives and Consumers. That’s the purpose of the chart. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l2 level1 lfo6'>Revamped the blue book flow to show all the adapters, deleted the AAL.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l2 level1 lfo6'>Only showed one Archive Generic Adapter and explained (with asterisk) that there’s one for each archive instantiation. Didn’t address whether one Blue Book might cover all Archives, or individual archives might adapt their own instantiation of an Archive Generic Adapter. Or that the User and Archive generic adapters might be the same. (Effectively the Abstraction Layer reincarnate) <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l2 level1 lfo6'>Showed multiple examples of Archive Specific Adapters and explained them in the note. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l2 level1 lfo6'>Left the RepInfo standards and XFDU standard “floating” without connection to this flow, per earlier note from John. <o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Comments, recommended changes are of course welcome. I think as it is, this is OK to plug into the Green Book and also to show to Peter for the Doc Tree discussion. Steve, note that the Blue Book you’ll show him is not yet lined up with this Doc Tree. I guess the question for him is whether we should go to the trouble of revamping the content of the Blue Book per this doc tree, and if so, what parts of the Blue Book get farmed out to which adapters? Or does he suggest something else? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If updates are needed, we should update in this file on the DropBox, then copy into the Green Book or presentations or wherever needed. This file should be the master for the Doc Tree. Except maybe chart 3. It’s “master” might need to be in a separate file, but not sure what. <o:p></o:p></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#002060'>That’s it for today. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><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><a href="https://public.ccsds.org/about/ManagementCouncil/MikeKearney.aspx">Mike Kearney</a><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><p class=MsoNormal><a href="mailto:KearneySolutions@gmail.com"><span style='color:blue'>KearneySolutions@gmail.com</span></a><span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><a href="mailto:MikeK@spacestandards.org"><span style='color:blue'>MikeK@spacestandards.org</span></a><span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>+1-256-361-5411 (mobile)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#002060'>Member of Technical Staff<o:p></o:p></span></p><p class=MsoNormal><a href="http://spacestandards.org/"><span style='color:blue'>Space Infrastructure Foundation</span></a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>