<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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>Dear all,</div>
<div> </div>
<div>Please find below the proposed agenda for tomorrow telecon:</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<ol style="margin:0;padding-left:36pt;">
<li>PAIS tutorial: </li></ol>
<ol type="a" style="margin:0;padding-left:72pt;">
<li>ISEE and SAFE test cases: discussion (emails from Mike 22/07, comments from Daniele 13/08)</li><li>Tutorial (Stephane?)</li><li>METS test case: first comments, organization (email from Daniele 13/08)</li></ol>
<ol start="2" style="margin:0;padding-left:36pt;">
<li>Information Curation Process: comments on documents sent by John (email from John, 11/08)</li><li>Other topics:</li></ol>
<ol type="a" start="4" style="margin:0;padding-left:72pt;">
<li>DAI registry <a href="http://www.sanaregistry.org/r/daixml/daixml.html"><font face="Times New Roman" size="3" color="blue"><span style="font-size:12pt;"><u>http://www.sanaregistry.org/r/daixml/daixml.html</u></span></font></a><font face="Times New Roman" size="3"><span style="font-size:12pt;">
</span></font>(link towards CCSDS publication page)</li><li>PAIS and ISO (20104)</li><li>Next meeting preparation (topics, availability, constraints for agenda)</li></ol>
<ol start="4" style="margin:0;padding-left:36pt;">
<li>Review of actions (email from John 10/08)</li></ol>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><u>Future</u><u> telecon</u><font face="Times New Roman" size="3"><span style="font-size:12pt;"><b>: </b></span></font><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font> </div>
<div><b>* Thursday 4</b><font size="1"><span style="font-size:5pt;"><b><sup>th</sup></b></span></font><b> September</b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font color="#1F497D"><u>If available, I propose to use Dave's number:</u></font></div>
<div>Dave Williams<br>
Telecon information <br>
+1-877-954-3555 USA Toll free <br>
+1-517-224-3191 Others <br>
Passcode: 8506950</div>
<div> </div>
<div>Best regards,</div>
<div> </div>
<div>Daniele </div>
<div>___________________________________________________________________________________________________________</div>
<div><font size="4" color="red"><span style="font-size:14pt;"><b>18 July minutes</b></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>DB: Daniele Boucon</div>
<div>DS: Don Sawyer</div>
<div>JG: John Garrett</div>
<div>MM: Mike Martin</div>
<div>SM: Stephane Mbaye</div>
<div>WG: all</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><span style="background-color:aqua;"><b>D=Decision, A=action</b></span><b> (other = discussion)</b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>1.</b> <b><u>SANA DAI registry </u></b><a href="http://beta.sanaregistry.org/r/daixml/daixml.html"><font face="Times New Roman" size="3" color="blue"><span style="font-size:12pt;"><u>http://beta.sanaregistry.org/r/daixml/daixml.html</u></span></font></a></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Short descriptions for SANA discussed during the meeting for common types, Collection and Transfer Object Descriptors, SIP constraints.</div>
<div>Descriptions for SIP model and XFDU: sent by Don just after the meeting.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><a href="http://beta.sanaregistry.org/r/daixml/ccsds-pais-common-types.xsd"><font face="Arial" size="2" color="blue"><span style="font-size:10pt;"><u>ccsds-pais-common-types.xsd</u></span></font></a><font face="Arial" size="2"><span style="font-size:10pt;"> :
</span></font><font face="Calibri" size="2"><span style="font-size:10pt;">common complex types used by other Producer Archive Specification Interface schemas</span></font></span></font></div>
<div><font size="2"><span style="font-size:10pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><a href="http://beta.sanaregistry.org/r/daixml/ccsds-pais-descriptor-collection.xsd"><font face="Arial" size="2" color="blue"><span style="font-size:10pt;"><u>ccsds-pais-descriptor-collection.xsd</u></span></font></a><font face="Arial" size="2"><span style="font-size:10pt;"> :
this schema characterizes one or more collection views of the objects to be transferred by a Producer to an Archive.</span></font></span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><a href="http://beta.sanaregistry.org/r/daixml/ccsds-pais-descriptor-transfer-object.xsd"><font face="Arial" size="2" color="blue"><span style="font-size:10pt;"><u>ccsds-pais-descriptor-transfer-object.xsd</u></span></font></a><font face="Arial" size="2"><span style="font-size:10pt;"> :
this schema characterizes the Digital Object Types of the objects to be transferred by a Producer to an Archive.</span></font></span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><a href="http://beta.sanaregistry.org/r/daixml/ccsds-pais-sip-constrainsts.xsd"><font face="Arial" size="2" color="blue"><span style="font-size:10pt;"><u>ccsds-pais-sip-constrainsts.xsd</u></span></font></a><font face="Arial" size="2"><span style="font-size:10pt;"> :
this schema characteriz</span></font><font face="Arial" size="2"><span style="font-size:10pt;"><i>es</i></span></font><font face="Arial" size="2" color="#18376A"><span style="font-size:10pt;"><b><i> </i></b></span></font><font face="Arial" size="2"><span style="font-size:10pt;">on
one side the authorized content of each SIP (Submission Information Package), on the other side the order in which SIPs have to be delivered by the Producer to the Archive.</span></font></span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><a href="http://beta.sanaregistry.org/r/daixml/ccsds-pais-sip-model.xsd"><font face="Arial" size="2" color="blue"><span style="font-size:10pt;"><u>ccsds-pais-sip-model.xsd</u></span></font></a><font face="Arial" size="2"><span style="font-size:10pt;"> :
this schema, used in conjunction with the schema for the XFDU packaging standard, characterizes the organization of the data within the SIP to be sent by the Producer to an Archive.</span></font></span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><a href="http://beta.sanaregistry.org/r/daixml/xfdu0.xsd"><font face="Arial" size="2" color="blue"><span style="font-size:10pt;"><u>xfdu0.xsd</u></span></font></a><font face="Arial" size="2"><span style="font-size:10pt;"> :
this schema characterizes the organization of data for transfer as a package between parties by providing a number of potentially useful attributes including, but not limited to, sequence, hierarchy, checksums, and global information about the whole package.</span></font></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>=> A (WG): </b>validate the SIP Model and XFDU descriptions for SANA<b>.</b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>=>A (DB): </b>send the descriptions to SANA; ask to replace “xfdu0” by “xfdu” in the registry table; give OK to open the DAI registry to all.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>2.</b> <b><u>Green Book: Final validation of ESA-SAFE test case</u></b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Last version updated following the previous telecom and validated by ESA sent the 15<font size="1"><span style="font-size:5pt;"><sup>th</sup></span></font> July.</div>
<div>Discussion to avoid ambiguity with the zip form in the simple case.</div>
<div> </div>
<div>DS: change in the first label table E-3: “Data as described” instead of “Data organization”.</div>
<div> </div>
<div><b>=>A (DB):</b> change in the text</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>=>A (WG):</b> give final comment on the ESA test case by next week.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> <font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></span></font></div>
<div><b><u>3. Green Book: Review of ISEE test case</u></b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>see Don’s email 27 June , Daniele’s emails 10 and 16 July.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Discussion on the way to explain how to use the PAIS through the test cases and core of the document.</div>
<div>SIP part: clarify how the XFDU looks like.</div>
<div> </div>
<div><b>=>A (DS):</b> finish the SIP part of the ISEE test case.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b><u>4. CNES CCSDS internal meeting</u></b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Budget granted for the preservation process.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Decision for CNES to work on the XML schema implementation of the DEDSL (already agreed at CCSDS management level). Question of 1 prototype only, while 2 are officially required for a blue book. </div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>The XML version of the control authority is also under schedule. Is that standard still used? </div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>=>A (JG</b>): ask NSSDC about the control authority standard</div>
<div> </div>
<div><b>=>A (WG):</b> plan the DEDSL project (currently behind schedule). Move the plan of the XML control authority.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b><u>5. LOTAR meeting</u></b></div>
<div>Held 24<font size="1"><span style="font-size:5pt;"><sup>th</sup></span></font> June (current CCSDS work presented by Daniele).</div>
<div>LOTAR is very interested in the preservation plan (should be included in the preservation process).</div>
<div>Meeting to be planned between Daniele and LOTAR’s chairman for inputs.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b><u>6. LTDP meeting (9-10 July) and Information Préservation Process</u></b></div>
<div>Updated version of the LTDP workflow (UML diagrams).</div>
<div>Daniele and John will work together beginning of August (terminology, …) for discussion for the 14<font size="1"><span style="font-size:5pt;"><sup>th</sup></span></font> telecom.</div>
<div> <font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>7. <b><u>Other points</u></b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Mike remarks that “If one does a google search for "producer archive interface specification" the two year old red book comes up first on the list. “</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>=>A (DB</b>): ask Brian Oliver for a solution to improve the access to PAIS blue book when searching wit internet.</div>
<div> </div>
<div>6. <b><u>Actions review</u></b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>To be done next time.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font size="4" color="red"><span style="font-size:14pt;"><b>End of 18 July minutes</b></span></font></div>
<div>___________________________________________________________________________________________________________</div>
<div><font size="4" color="red"><span style="font-size:14pt;"><b>Historical minutes</b></span></font></div>
<div>___________________________________________________________________________________________________________</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> 2. <font face="Calibri" size="2"><span style="font-size:11pt;"><b><u>GREEN BOOK</u></b></span></font></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> <font face="Calibri" size="2"><span style="font-size:11pt;"><b>2.1 </b></span></font><font face="Calibri" size="2"><span style="font-size:11pt;"><b><u>TOC for test cases</u></b></span></font></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>* on the content of the sections,</b></div>
<div><b>* on the title of the sections</b></div>
<div><b>* on the following question:</b><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font>is that better to describe the SIP constraints with the MOT (in section 6.1.3), or in a global section on SIPs (section 6.1.4)?</div>
<div> </div>
<div>Discussion: </div>
<div>Brief introduction about the sub-TOC by Stephane.</div>
<div>John and Don: <i>6.1.4.1 SIP constraints, included in 6.1.3</i></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>Current Structure:</b></div>
<div><span style="text-transform:uppercase;"><b>6</b></span>... <span style="text-transform:uppercase;"><b>Use Cases. 6-1</b></span></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><span style="text-transform:uppercase;">6.1</span><font size="2"><span style="font-size:11pt;"> </span></font><span style="text-transform:uppercase;"><i>NAME</i></span><span style="text-transform:uppercase;">
– </span><span style="text-transform:uppercase;"><i>TITLE</i></span><span style="text-transform:uppercase;">.. 6-1</span></span></font></div>
<div><span style="text-transform:uppercase;">Description</span></div>
<div><span style="text-transform:uppercase;">6.1.1</span> <i>TEST_CASE_</i><span style="text-transform:uppercase;"><i>NAME</i></span><span style="text-transform:uppercase;"> DATA SET</span></div>
<div><span style="text-transform:uppercase;">6.1.2</span> <i>TEST_CASE_</i><span style="text-transform:uppercase;"><i>NAME</i></span><span style="text-transform:uppercase;"> MOT AND SIP CONSTRAINTS</span></div>
<div><span style="text-transform:uppercase;">6.1.4</span> <i>TEST_CASE_</i><span style="text-transform:uppercase;"><i>NAME</i></span><span style="text-transform:uppercase;"> SIPS</span></div>
<div> </div>
<div> </div>
<div><b>Decision on the Structure:</b></div>
<div><span style="text-transform:uppercase;"><b>6</b></span>... <span style="text-transform:uppercase;"><b>Use Cases</b></span></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><span style="text-transform:uppercase;">6.1</span><font size="2"><span style="font-size:11pt;"> </span></font><span style="text-transform:uppercase;"><i>NAME</i></span><span style="text-transform:uppercase;">
– </span><span style="text-transform:uppercase;"><i>TITLE</i></span><span style="text-transform:uppercase;">.</span></span></font></div>
<div><span style="text-transform:uppercase;">6.1.1</span> <span style="text-transform:uppercase;">Context And Benefits</span></div>
<div> <span style="text-transform:uppercase;"><i>Contains description + what this test case shows</i></span></div>
<div><i> give explanation at the beginning of each test case of the specificity of the test case, and how the method applies</i></div>
<div><span style="text-transform:uppercase;">6.1.2</span> <span style="text-transform:uppercase;">Objects to be transferred</span></div>
<div> <span style="text-transform:uppercase;">same as </span><i>TEST_CASE_</i><span style="text-transform:uppercase;"><i>NAME</i></span><span style="text-transform:uppercase;"> DATA SET</span><span style="text-transform:uppercase;"><i>: contains the
description of all the information (data, documents, …) that have to be transferred, and how this information is organized on the producer side</i></span></div>
<div><span style="text-transform:uppercase;">6.1.3</span> <span style="text-transform:uppercase;">Model OF OBJECTS For transfer and sip constraints</span></div>
<div> <span style="text-transform:uppercase;"><i>contains the description of the mot and the sip types and sequencing constraints</i></span></div>
<div><span style="text-transform:uppercase;">6.1.4</span> <span style="text-transform:uppercase;">sips</span></div>
<div> <i>Contains the description if SIP IMPLEMENTATION AND TRANSFER</i></div>
<div> <i>Contains an example of SIP manifest.</i></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>___________________________________________________________________________________________________________</div>
<div><b><u>2. GREEN BOOK</u></b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> <font face="Calibri" size="2"><span style="font-size:11pt;"><b>2.2 </b></span></font><font face="Calibri" size="2"><span style="font-size:11pt;"><b><u>Test cases review</u></b></span></font></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b><u>2.2.3 ESA-SAFE test case</u></b></div>
<div>The 2 models have been shown during the 19-20 March LTDP meeting.</div>
<div>Exchanges between CNES, Gael and ESA on data sets.</div>
<div>First version of the green book part -> to be first reviewed by Daniele and Stephane, then send to the group.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>==> <u>Action Daniele (with Stephane)</u>: review the ESA SAFE test case, then send it to the group.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> <font face="Calibri" size="2"><span style="font-size:11pt;">LTDP actions (from 7th November meeting)-> </span></font><font face="Calibri" size="2"><span style="font-size:11pt;"><b><u>closed</u></b></span></font><font face="Calibri" size="2"><span style="font-size:11pt;">
during the 19-20 March meeting</span></font></span></font></div>
<table width="790" style="width:474.3pt;margin-left:62.9pt;">
<col width="32" style="width:19.5pt;">
<col width="87" style="width:52.5pt;">
<col width="109" style="width:65.55pt;">
<col width="561" style="width:336.75pt;">
<tr height="32" style="height:19.35pt;">
<td><font face="Times New Roman" size="2"><span style="font-size:9pt;">25.3</span></font></td>
<td><font face="Times New Roman" size="2"><span style="font-size:9pt;">CNES/GAEL</span></font></td>
<td><font face="Times New Roman" size="2"><span style="font-size:9pt;">LTDP_WG#26</span></font></td>
<td><font face="Times New Roman" size="3"><span style="font-size:12pt;">Model the SIP Data Objects at the level of SAFE Metadata and Data Object in order to allow the transfer of sub-parts of SAFE products in different SIPs</span></font></td>
</tr>
<tr height="32" style="height:19.35pt;">
<td><font face="Times New Roman" size="2"><span style="font-size:9pt;">25.4</span></font></td>
<td><font face="Times New Roman" size="2"><span style="font-size:9pt;">ESA/PS</span></font></td>
<td><font face="Times New Roman" size="2"><span style="font-size:9pt;">End November 2013</span></font></td>
<td><font face="Times New Roman" size="3"><span style="font-size:12pt;">Gather any useful documents to allow the prototype development/tailoring and provide the EO-SIP of ERS for Test.</span></font></td>
</tr>
</table>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b><u>2.3 ISEE1-2 test case</u></b></div>
<div>Test case nearly finished.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Mail sent by Don 5th May "Partial update for Section 6.1": material for "ISEE - a typical use case"</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>MM: the history of the test case is not useful in the Green Book (was ok in the yellow book). Needs to show clear test cases -> highlight what the test case brings. </div>
<div> </div>
<div>DB: this test case shows the main features of the PAIS. Could have interest showing the differences between how the data are organized on the Producer side, how the data are modeled in the MOT (intermediary repositories may not be modeled with groups),
how they are gathered in SIPs?</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>SM: the attached files (descriptors …) could be put at the end of each specific test case part, and then at the end we'll see how to organize the whole document gathering the different test cases.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b><u>2.4 COROT test case</u></b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Daniele explains that CNES is pushing to get the CoRoT L0 data use case (from Daniele and Stephane) – for information this has to be finished by 13 May to get a chance to be used for L1 data.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b><u>2.5 METS test case</u></b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Daniele had a meeting (9 April) with BNF that could help building a METS implementation of SIPs (documents).</div>
<div>Daniele introduces the need from BnF of transferring references to objects instead of the target objects themselves.</div>
<div>Stephane: this is ok for XFDU</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>=> <u>Action Stephane</u>: Provide example of XFDU with referenced data objects (remote URL or URI)</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Don finds a priori relevant</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Decision: Nothing to do on that topic until further inputs from Bn</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b><u>2. PDS4 test case </u></b></div>
<div> </div>
<div>Mail sent by Mike (5h May): 2 figures and text for section 6.3 "Planetary Data System - a non XFDU implementation"</div>
<div> </div>
<div>Discussion on figure "PDS4 Bundle and Collection linkages": this is the current PDS4 Bundle description. </div>
<div>Data are localized via URN.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>MM: this figure is an overview of what the PDS4 bundle looks like. Same for every PDS archive. The test data sent before conform to this generic figure.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Figure "PDS4 SIP Organization"</div>
<div>MM: for NSSDC, show that Manifest is better than bundle level.</div>
<div> </div>
<div> </div>
<div>Mike has sent a complete email to Daniele concerning the CNES PAIS software (issues, context and associated files).</div>
<div>For the moment, Daniele is looking for a MAC machine to re-play the scenario in order to be able to undrestand the problems.</div>
<div>Mike will try it on a PC.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>=> <u>Action Daniele</u>: deliver the CNES proto software to John (ASAP)</div>
<div> </div>
<div><font face="Consolas" size="2"><span style="font-size:10.5pt;">There was a brief discussion of Mike’s e-mail (4th December) addressing the PDS4 Bundle organization and Don’s e-mail response (19th December) with possible modeling options. Mike agreed that
a hierarchy is a requirement for a bundle. Don gave two options. The first is a single Collection Descriptor holding a single Transfer Object, where the ‘group’ capability of the TO is used to completely model the bundle with the option of cutting off the
modeling at any point by use of the ‘undescribed’ attribute. This approach would be consistent with past PDS/NSSDC practice of transferring a PDS volume to NSSDC with the only requirement on NSSDC being the ability to return the volume unaltered. In other
words, PDS did not expect NSSDC to look into the volume and provide any services, such as replacement, at a lower level of granularity. The second option would be to model the bundle as composed of multiple Transfer Objects under multiple Collection Descriptors.
For example, there would be a set of Collection Descriptors corresponding to the PDS4 standard named collections, and under each of these there would be Transfer Objects and possibly more Collection Descriptors. There are a lot of possibilities for how the
resultant model might look. The advantage of modeling a bundle as consisting of multiple TOs is that it facilities replacement at the TO level, rather than the whole bundle, if that becomes a requirement. Regardless, it should not be too difficult to have
PDS4/NSSDC specific software what would start from a basic bundle model and then create a complete MOT by examining an existing bundle. It could be integrated with a SIP builder, but it would probably be preferable to have the MOT exchange with NSSDC prior
to any SIP exchange to reduce confusion and ensure both parties were ‘on the same page’.</span></font></div>
<div><font face="Consolas" size="2"><span style="font-size:10.5pt;"> </span></font></div>
<div><font face="Consolas" size="2"><span style="font-size:10.5pt;">Don agreed to look at Mike's example Descriptors to see how they might fit into the above options.</span></font></div>
<div> <font face="Consolas" size="2"><span style="font-size:10.5pt;"> </span></font></div>
<div><font face="Consolas" size="2"><span style="font-size:10.5pt;">==> <u>action Mike</u>: send samples of data </span></font></div>
<div> </div>
<div>What could really help in the use of the PAIS by the PDS, is a proposal of implementation without use of XFDU. To be done.</div>
<div>Suggestion from John: use XFDU, and then an XSLT style sheet to translate into another language (to be confirmed, not sure my understanding was correct).</div>
<div> </div>
<div>A PDS product = a Transfer Object.</div>
<div>A bundle = PDS tree data set. The size of the bundle is 1.7 Go, but files inside are quite small, around 250 ko).</div>
<div> </div>
<div>==> <u>Action Stephane</u>: propose a SIP implementation without XFDU</div>
<div> </div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> <font face="Calibri" size="2"><span style="font-size:11pt;">==> </span></font><font face="Calibri" size="2"><span style="font-size:11pt;"><u>action all</u></span></font><font face="Calibri" size="2"><span style="font-size:11pt;">:
send comments on Mike's information on PDS4 sample (email 30th October)</span></font></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>22 April telecon: From file : met_abstract_sip_manifest.xml</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>MM: The file is a <u>flat</u> list of PAIS elements from SIP Model (PAIS BB §6) and some elements deriving from XMAN (PDS4).</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>SM: sent a tc5-pds4-20140401.pdf providing an example of Non-XFDU SIP implementation also reusing the SIP Model elements from PAIS BB §6, but with a structure of nested elements.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>DS: reminds that nesting is not mandatory with respect to the PAIS BB §5 abstract SIP model. The structure of the manifest may depend from the context and what the Producer and the Archive actually want to convey.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>SM: agrees that the provided example(s) are not implementing the PAIS BB §5 from scratch but are all reusing the SIP Model elements built for XFDU but getting rid of the XFDU elements. This may be confusing.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>SM: the elements of the SIP Model built for XFDU require a nested structure, at least to identify to which Group occurrence a Data Object belongs to, or to which Transfer Object occurrence a Group instance belongs to. Alternate elements could have allowed
a flat structure as for XMAN.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>WG: The WG agrees that this in-between implementation may be confusing in the GB and a fully independent implementation should be preferred.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>WG: agrees that a table, a checklist or any other means that could help a user validating./tracking the level of implementation could be helpful in the GB e.g. is the Goup ID identified, is the SIP ID provided, other IDs, MIME types, etc.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>__________________________________________________________________________________________________________</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> 2. <font face="Calibri" size="2"><span style="font-size:11pt;"><b><u>GREEN BOOK</u></b></span></font></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>The Green Book has been split into several files, one for the core, and one per test case.</div>
<div> </div>
<div>=> <u>Action Stephane</u>: provide a description of the document breakdown and links to the shared repository</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> <font face="Calibri" size="2"><span style="font-size:11pt;"><b>2.3 </b></span></font><font face="Calibri" size="2"><span style="font-size:11pt;"><b><u>Core document</u></b></span></font></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Section 4.1.1 reviewed (ok)</div>
<div>Tabular representation is welcome but question remains about their systematic use (need an XML version in annex ?)</div>
<div> </div>
<div>CCSD0014: equivalent to TO Descriptor, and CCSD0015: equivalent to Collection Descriptor</div>
<div> </div>
<div>==> <u>Action Stephane</u> from MM: explain more the CCSD0015: how it is registered and reference where more information could be found on that subject</div>
<div> </div>
<div>Don: descriptorModelID has to be changed on any XSD change (specialization), the Archive has to maintain the versions</div>
<div> </div>
<div>Section 4.6.1 about PAIS XSD description should remain here for the time being</div>
<div> </div>
<div>John: The SANA registry is supposed to reference the (latest ?) PAIS XSD only (TBC). It is however sure that it should not contain any other resource e.g software, XML examples, etc.</div>
<div> </div>
<div>« open » enumeration technique is cumbersome (TBC)</div>
<div> </div>
<div>==> <u>Action (All):</u> table in section 4.6.4 should be reviewed for (during) next telecon</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Comment from previous telecons on method </div>
<div>* (Daniele): there are steps that conform to the PAIMAS process (first model, SIP constraints, then transfer and validation).</div>
<div>* Link between the data base on the Archive side, and the PAIS XML elements: example on how to match both (core document, test case?).</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>The following paragraph will be suppressed if ok:</div>
<div><font size="2"><span style="font-size:10pt;"><b><u>XML namespace for PAIS </u></b></span></font></div>
<div> <font color="#1F497D"> </font></div>
<div>John suggested that we pass the proposal on namespaces by SANA and Nestor and Peter as XML Co-chairs to make sure they agree.</div>
<div> </div>
<div>==> <u>action Stephane (20130821)</u><font color="#1F497D"><b><i>: </i></b></font>send proposal on namespace to SANA, Nestor and Peter, and ask if they have any objection to our proposal. </div>
<div><font size="2"><span style="font-size:10pt;">Use previous email sent by John to introduce Stephane in the group.</span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>It is agreed that not all positions where a pais :any element are possible have to be documented in the GB. Only a few example are necessary or even one.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>More concrete example should be provided than the abstract « foo »/« bar » currently proposed. Typical example would be a Collection holding a pais :any with the author of the descriptor, the Collection name/ID in the Producer semantic, or anything else
that could be specific to the Producer or the Archive side but not provided in the PAIS definitions.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>For time constraints, the WG jumped to the section 4.6.4 of the draft GB.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>SM: Reminded that « true » restrictions of XML Schema guarantees that the original PAIS XML Schema’s rule are still applicable. Any instance following a restriction follows the original ones.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>SM: The use of restrictions does not impose any system to use the derived PAIS schemas. Therefore, the restricted schemas have not to be shared with any user of the produced SIPs. The project specific schemas could even be discarded without losing control
of the produced SIPs.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>=> D – (DS) The rightmost column of the table in §4.6.4 shall be renamed « Restriction » instead of « Content »</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>MM: It is not clear that this table should be kept in that form or discarded at the end, but the target should not spend too much pages on that topic.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>WG: restrictions may be interesting for implementers and as such should be documented, but it is not clear if this should be proposed as a recommendation or a best practice.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>SM: reminded that restricting elements such as the maxOccurrence’s should be a recommended practice since it can be very difficult to implement interoperable software exchanging elements of xs:nonNegativeInteger type.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>SM: proposed to add prepared templates of restricting XML Schemas in annex. Something that could help implementers to quickly setup the restrictions of their needs.</div>
<div>WG: adding XML Schema’s in annex may not be so helpful because cut and paste from PDF may be very cumbersome.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>=> D – (JG) these XSD shall be placed side to the originals.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>SM: The problem is similar to other GB resources as the use case descriptors or the software prototypes.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>___________________________________________________________________________________________________________</div>
<div> </div>
<div><b><u>Preservation process </u></b></div>
<div> </div>
<div>DB: LOTAR representative is ok with "preservation", but not with "curation" (this word is not used in the community).</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>MM: links should be made between MTDP and warehousing. Not clear with the structure of the process for the moment.</div>
<div> </div>
<div>Discussion on terminology: preservation vs curation.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>LTDP definitions: </div>
<ul style="margin:0;">
<li style="margin-top:5pt;margin-bottom:5pt;"><b>Preservation:</b> aims at the generation of a single, consistent, consolidated and validated <b><i>“EO Missions/Sensors Dataset” </i></b>and at ensuring its long term integrity, discovery, accessibility and usability.
It is focused on an individual Mission/Sensor or on a multi-mission Dataset (when one Master Dataset is made up of data coming from different missions/sensors) and tailored according to its specific preservation/curation requirements. It consists of all activities
needed to ensure “EO Missions/Sensors Dataset” bit integrity over time and to optimize (in terms of format and coverage) its (re)use in the long term (e.g. through metadata and catalogue improvement, algorithms evolutions and related (re)processing, linking
and improvement of context/provenance information).</li><li style="margin-top:5pt;margin-bottom:5pt;"><b>Curation: </b>aims at establishing and increasing the value of <b><i>“EO Missions/Sensors Datasets” </i></b>over their lifecycle, at favouring their exploitation through the combination with other Datasets and
at extending their user base. It includes the activities for the definition of the preservation objectives, for the coordination and management of Data Time Series and Collections (e.g. from similar sensor family) in support to specific applications. It includes
international cooperation activities</li></ul>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>OAIS definitions:</div>
<div><b>Long Term Preservation</b>: The act of maintaining information, Independently Understandable by a Designated Community, and with evidence supporting its Authenticity,</div>
<div>over the Long Term.</div>
<div><b>Authenticity</b>: The degree to which a person (or system) regards an object as what it is purported to be. Authenticity is judged on the basis of evidence.</div>
<div> </div>
<div>Authenticity: in the sense of "original". This is not crucial in the domain of scientific data, but is an issue. Integrity could be a way to prove authenticity.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>We note that the LTDP definitions are not clear nor completely coherent. There is a mixture of both preservation/curation concepts in both definitions.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>Furthermore, the group thinks that the term "curation" used in the LTDP definition does not fit the usual usage, another term should be used. The sens is nearer of knowledge management. </div>
<div>Daniele will send tomorrow a summary of her comments.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;">=> <font face="Calibri" size="2"><span style="font-size:11pt;"><u>Action Daniele</u></span></font><font face="Calibri" size="2"><span style="font-size:11pt;">: ask David for preservation/curation
definition.</span></font></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;">=> <font face="Calibri" size="2"><span style="font-size:11pt;"><u>Action all</u></span></font><font face="Calibri" size="2"><span style="font-size:11pt;">: give comments and proposals
as input for the LTDP terminology and steps of workflow. -> </span></font><font face="Calibri" size="2"><span style="font-size:11pt;"><b><u>for Monday at the latest.</u></b></span></font></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><u>Previous discussion:</u></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>To be done: analyse and suggest, at different stages of the project (during data lifecycle), what should be done on an archiving point of view.</div>
<div> </div>
<div>Example of main issue: keep documentation up to date (when changes in formats, processing, … are made on the data).</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>The LTDP has written a document "PDSC" (Preservation Data Set Content), explaining what kind of information (data, software, documents, …) should be collected and at what step of the project.</div>
<div> </div>
<div>The subject is wide, Mike asks to focus on specific parts.</div>
<div> </div>
<div>Daniele explains her point of view: develop a "model" (magenta book) gathering all the basic components of the preservation activity (selection and appraisal, data and metadata preparation, access, maintenance …) that should cover all the data lifecycle
(even when data don't exist), in order to be able to answer the following question: what should be done from the beginning till the end to be able to preserve data, and at what moment? This should be done in a generic way, making links on standards related
to basic components when they exist.</div>
<div> </div>
<div>Suggestion to ask Barbara Sierman of existing works concerning this topic. Mail sent the 7/02 by Daniele.</div>
<div> </div>
<div>==> <u>Action Daniele</u>: write and send more precise elements on this process to the group.</div>
<div> </div>
<div>==> <u>Action all</u>: send comments.</div>
<div><font color="red"> </font></div>
<div>Nestor will send for the new project approval once the ¨PAIS BB has been published.</div>
<div> </div>
<div>Daniele underlines the need for CNES and LTDP group. CCSDS expertise will be very important.</div>
<div> </div>
<div>The PDS has its internal process ; for other agencies (particularly the LTDP member agencies) this process doesn't exist and is required.</div>
<div> </div>
<div>Question on how to make the link between a global process and the PAIMAS phases.</div>
<div> </div>
<div>20131030 Don's email and following discussions:</div>
<div>Don: The process could be focussed on the Archive point of view, and seen an internal OAIS issue for workflow, using then more OAIS concepts.</div>
<div>The "provenance" is practically a big issue, going back to the original information.</div>
<div>"Reprocessing, curation, stewardship" could be maped with OAIS migrations, new versions, …</div>
<div> </div>
<div>Update procedures exist at NSSDC.</div>
<div> </div>
<div>Daniele: appraisal should be the starting point. Workflow, on the Archive side, could begin early in a space project, even when data don't yet exist ; link with the Archive side of the PAIMAS.</div>
<div> </div>
<div>=> <u>action all</u>: exchange on high level process (3 main steps preparation/preservation/maintenance) and links with PAIMAS phases for return to the LTDP group.</div>
<div> </div>
<div>==> <u>action Daniele</u>: follow the work of LTDP group on preservation process, and send all available information to the DAI group on this subject.</div>
<div> </div>
<div>Need for return on the preservation process from all.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>___________________________________________________________________________________________________________</div>
<div><b><u>Other subjects </u></b></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><br>
<font face="Calibri" size="2"><span style="font-size:10pt;"><b><u>OAIS Magenta Book (French version)</u></b></span></font><font face="Calibri" size="2" color="#1F497D"><span style="font-size:10pt;"><b> </b></span></font></span></font></div>
<div> </div>
<div>Daniele has received the complete updated French version.</div>
<div>Complete validation to be performed now (text and figures)</div>
<div>This version will be also validated by the French National Archives.</div>
<div>Due to the amount of work on the PAIS, and priority to the PAIS green book, this will be treated after.</div>
<div> <font color="#1F497D"> </font> </div>
<div><b><u>XML schema for DEDSL </u></b></div>
<div>Seems possible for CNES to write the document on the model on the existing other DEDSL standards. At CNES, XML schema for DEDSL is already created and implemented.</div>
<div>Prototypes: CNES has already tested it on operational tool. This could play the role of prototype, and this could be enough.</div>
<div> </div>
<div>Nestor explained John that a 2nd prototype is required.</div>
<div><font color="#1F497D"> </font></div>
<div>A possibility could be to produce not a blue book, but a document that won't required 2 prototypes (orange book). To be more discussed.</div>
<div> </div>
<div><font color="#1F497D">____________________________________________________________________________________________</font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
</span></font>
</body>
</html>