<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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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:1426614265;
mso-list-type:hybrid;
mso-list-template-ids:-25541836 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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;}
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>Today’s telecon had a soul-searching discussion of what an ADD (Architecture Description Document) is, and what the Blue book that we’re currently developing is. Steve described it’s tendency towards focusing on the details of the Archive Abstraction Layer, and hence we began to discuss whether the content currently in the blue book is really ADD material or AAL Blue Book material. This led to a discussion where I said we should have a document tree, so naturally I got the action to build it. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Attached is a PPT with a first notional cut at a document tree. I’ll also suggest that a Doc Tree figure should actually be in the ADD, or even perhaps the OAIS Reference Model document (next revision, of course). This ADD after all, is intended to be the ADD for the OAIS-IF, not an overall OAIS architecture. The OAIS-IF ADD is subordinate to the OAIS RM, not the other way around. I did not try to include the shadow-organization of an ISO Doc Tree. To be complete we should probably do that, and spell out acronyms. Right now I consider this a working document for us insiders. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A few comments are in the notes of the PPT charts. Two additional charts from IPELTU and our CMC material are added for reference. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Some background on ADDs: There is only one other in CCSDS, for Cross Support, the CCSS-ADD, and it is here:<o:p></o:p></p><p class=MsoNormal><a href="https://public.ccsds.org/Pubs/901x0g1.pdf">https://public.ccsds.org/Pubs/901x0g1.pdf</a><o:p></o:p></p><p class=MsoNormal>It is a green (informative, not normative) book, and it has a companion Magenta book (an ARD – Architecture Requirements Document). The ARD is not in our plan. We could conceivably have a magenta ADD that includes normative requirements like an ARD. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Some notable statements from the CCSS-ADD (relating them to our OAIS-IF ADD): <o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level1 lfo1'>The foreword on page ii says: The architecture described in this document was developed based on the Cross Support Reference Model…” Our counterpart statement is that our ADD is based on the OAIS Reference Model. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level1 lfo1'>Section 2.1, page 2-1: “The SCCS communications architecture reference model described in this document establishes a common framework that provides a basis for developing, providing, and using space communications cross support services.” Our ADD does the same for Archive Services. <o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level1 lfo1'>Section 2.2, page 2-1: “This SCCS-ADD Green Book provides the top-level description of the architecture elements of space communications cross support.” Our ADD should provide the top-level description of the architecture elements of the OAIS-IF. Seems to me that “Top Level” includes the entire UML chart that Steve has developed. However, Steve made verbal reference to focusing on the “gray/green boxes”. The document that focuses on the abstraction layer should be the Archive Abstraction Layer Blue Book. Our counterpart to the <a href="https://public.ccsds.org/Pubs/521x0b2e1.pdf">MAL</a>. <o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So there’s my notional Doc Tree, and how the ADD relates to it. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></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>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><p class=MsoNormal><o:p> </o:p></p></div></body></html>