<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>Hi all,</div>
<div> </div>
<div>Please find below the minutes for the today meeting. Please correct if I have forgotten important points, particularly on the SEA part.</div>
<div> </div>
<div>Best regards,</div>
<div> </div>
<div>Daniele</div>
<div> </div>
<ol style="margin:0;padding-left:36pt;">
<li>joint meeting SEA/DAI on DEDSL/XML implementation.</li></ol>
<div> </div>
<div>J. Garrett, D. Boucon, SANA team, Nestor Peccia, Peter Shame and the other members of SEA group.</div>
<div>Telecon : Beatrice Larzul (CNES)</div>
<div> </div>
<div>NP explains that the discussion must concern the comments on XML, rather than the use of this standard that is a different question out of the scope of this meeting.</div>
<div> </div>
<div>XML style: use of Upper case instead of Camel Case: it is important to keep the compatibility with the existing implementations (PVL, DTD), and have an XML updated version.</div>
<div> </div>
<div>But it is asked:</div>
<div> </div>
<div>1.to add also an other implantation taking into account the proposed future CCSDS rules (camel case style, versioning, namespace), for example in an annex.</div>
<div> </div>
<div>2.To add sections on “SANA considerations”, “Security”, “document patents” in the document,</div>
<div> </div>
<div>3.to register the XML schema, as well as the existing DTD to SANA (see other discussion below).</div>
<div> </div>
<div>Discussion on terminology: the process to update the terminology should be discussed next Monday during the CESG meeting.</div>
<div> </div>
<div>The following comment has been made: check the existing definitions in the CCSDS glossary when using new terms, and avoid too long definitions (such as it is the case for “Data Entity Dictionary”.</div>
<div> </div>
<div> </div>
<ol start="2" style="margin:0;padding-left:36pt;">
<li>Meeting with SANA</li></ol>
<div>Marc Blanchet SANA</div>
<div>Audric Schiltknecht SANA</div>
<div> </div>
<div><b>DEDSL and DTD</b></div>
<div style="padding-left:36pt;">Add a “SANA consideration” section in the DEDSL document containing the requests-> see examples on the SANA website.</div>
<div> </div>
<div style="padding-left:36pt;">=><u>Action DAI:</u> send an email to SANA requesting registration of DTD in the DAI registry, with the following: short description, DTD file, group “DEDSL”, reference to the standard</div>
<div style="padding-left:36pt;"> </div>
<div style="padding-left:36pt;">=><u>Action DAI</u>: send an email to SANA requesting registration of XML schema in the DAI registry, with the following: short description, schema file, group “DEDSL”, reference of the standard 647.4</div>
<div> </div>
<div style="text-indent:35.4pt;">=><u>Action SANA</u>: send DAI the guidelines for SANA</div>
<div> </div>
<ol style="margin:0;padding-left:36pt;">
<li>Namespace: write in “SANA consideration” section, a sentence requesting a namespace, and to register any DTD and schema.</li></ol>
<div> </div>
<div><b>DAI o</b><b>pen action</b><b> (CIO registry)</b></div>
<div>We have an old action concerning the registry of data formats associated with DAI standards :</div>
<table width="1396" style="width:838pt;margin-left:1.15pt;">
<col width="93" style="width:56pt;">
<col width="78" style="width:47pt;">
<col width="41" style="width:25pt;">
<col width="468" style="width:281pt;">
<col width="81" style="width:49pt;">
<col width="96" style="width:58pt;">
<col width="58" style="width:35pt;">
<col width="478" style="width:287pt;">
<tr height="44" style="height:26.45pt;">
<td style="text-align:right;"><font face="Arial" size="2"><span style="font-size:10pt;">2014-03-31</span></font></td>
<td><font face="Arial" size="2"><span style="font-size:10pt;">AI#24</span></font></td>
<td><font face="Arial" size="2"><span style="font-size:10pt;">DAI</span></font></td>
<td><font face="Arial" size="2"><span style="font-size:10pt;">Work with MB of SANA as required to ensure CCSD ADIDs in PAIS (and other DAI standards) are registered.</span></font></td>
<td><font face="Arial" size="2"><span style="font-size:10pt;">JGG</span></font></td>
<td><font face="Arial" size="2"><span style="font-size:10pt;">As needed</span></font></td>
<td><font face="Arial" size="2"><span style="font-size:10pt;">Open</span></font></td>
<td><font face="Arial" size="2"><span style="font-size:10pt;">20140605 - Registry has not yet been setup in SANA. DB will contact SANA regarding its status.</span></font></td>
</tr>
</table>
<div> </div>
<div style="text-indent:35.4pt;">=><u>Action JG</u>: regenerate the list of CCSDS ADIDs, and send it to SANA for creation of the CCSDS ADID registry.</div>
<div> </div>
<div><b>PAIS BB glossary</b></div>
<div> </div>
<div>=><u>Action DB</u>: send to SANA the spreadsheet of the <u>terms</u> and <u>abbreviations</u> included in the PAIS BB (the new ones appearing in italics for inclusion, the terms already defined in the glossary for reference to the PAIS BB).</div>
<div> </div>
<div>MOIMS plenary report</div>
<div>_____________________________ END OF THE MEETING ________________________________________</div>
<div> </div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>