<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> </div>
<div>Hi all,</div>
<div> </div>
<div>Please find below the minutes of today telecon. Feel free to correct or comment.</div>
<div> </div>
<div><u>Next telecon</u>:</div>
<div>Friday 30<font size="1"><span style="font-size:7.3pt;"><sup>th</sup></span></font> January (15h EU time, 9h US time-Washington)</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><u>Agenda for next telecon</u><u> (2 different parts</u><u> with corresponding timing</u><u>)</u>: </div>
<div>1<font size="1"><span style="font-size:7.3pt;"><sup>st</sup></span></font> hour: </div>
<div>* Corot test case </div>
<div>* Core GB </div>
<div>* METS test case </div>
<div>2<font size="1"><span style="font-size:7.3pt;"><sup>nd</sup></span></font> hour:</div>
<div>* ICP </div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font color="#1F497D"><u>If available, proposal to use Dave's new number for the sound</u><font color="red"><u>:</u></font></font></div>
<div>Dave Williams<br>
Telecon information </div>
<div>+1-844-467-6272 USA Toll Free</div>
<div>+1-720-259-6462 Others</div>
<div>Passcode: 841727</div>
<div> </div>
<div><font color="#002060"><u>To view screen and documents, please connect to the following :</u></font></div>
<table width="417" style="width:250.4pt;margin-left:6.3pt;">
<col width="0" style="width:0;">
<col width="417" style="width:250.4pt;">
<tr>
<td><font face="Times New Roman" size="3"><span style="font-size:12pt;"></span></font></td>
<td><font face="Times New Roman" size="3"><span style="font-size:12pt;"><a href="https://webconference.cnes.fr/ccsds_2015_jan_30/">https://webconference.cnes.fr/ccsds_2015_jan_30/</a></span></font></td>
</tr>
</table>
<div> </div>
<div>Attached is the updated list of Stephane’s action (John, could you please update the Action table with it?)</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>9</b><font size="1"><span style="font-size:6.3pt;"><b><sup>th</sup></b></span></font><b> </b><b>January</b><b> meeting minutes</b></span></font></div>
<div> </div>
<div>DB: Daniele Boucon </div>
<div>DG: David Giaretta </div>
<div>DS: Don Sawyer </div>
<div>ES: Esther Conway </div>
<div>JG: John Garrett </div>
<div>MM: Mike Martin (NASA)</div>
<div>RD: Robert Downs </div>
<div>SM: Stephane Mbaye</div>
<div>SR: Stephane Reecht</div>
<div>BC: Bertrand Caron (BnF)</div>
<div>PT: Philippe Tramoni (BnF)</div>
<div>WG: all</div>
<div> </div>
<div><span style="background-color:aqua;"><b>D=Decision, A=action</b></span><b> (other = discussion)</b></div>
<div> </div>
<div style="text-indent:-18pt;margin-top:5pt;margin-bottom:5pt;"><font size="4"><span style="font-size:14pt;">1.<font face="Times New Roman" size="1"><span style="font-size:7pt;"> </span></font><b>1</b><b> Information Curation Process -ICP</b></span></font></div>
<div>ICP is made up activities or grouping of activities, divided into levels and sub levels. Risk management is one of them. ICP should include a kind of roadmap, pointing out stages and where responsibility is handed over, instead of describing in details
each activity.</div>
<div>Where OAIS applies should be identified (from last minutes).</div>
<div> </div>
<div>MM: need for a framework showing how the activities fit together. The LTDP document recovers areas of OAIS + PAIS, thus making a redundancy with other standards.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>DG + DB: the LTDP document is at the starting point of the ICP. We need to be practical and to focus on the scope.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>All: LTDP document in the scope of EO and is very specific to EO. CCSDS needs to enlarge this scope to be generic with a broader set of activities.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>EC (information sent yesterday by email on risk and planning management): need to take into account the risk, and a more dynamic iterative system.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>D => (all):</b> framework, wider than EO domain, in the form of a draft document describing high level steps and referring to a number of area specific standards to be produced.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font size="4"><span style="font-size:14pt;"><b>2</b><b> </b><b>METS test case</b></span></font></div>
<div><font size="4"><span style="font-size:14pt;"> </span></font></div>
<div>Also see emails sent by SR the 7<font size="1"><span style="font-size:7.3pt;"><sup>th</sup></span></font> and 9<font size="1"><span style="font-size:7.3pt;"><sup>th</sup></span></font> January</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>New version sent the 3<font size="1"><span style="font-size:5pt;"><sup>rd</sup></span></font> December for review and discussion. Updates presented by SM (homogenization of terms in the text and in the implementation).</div>
<div> </div>
<div>BC: presentation of the new PAIS-METS Manifest. 3 possibilities: minimal PAIS implementation (1<font size="1"><span style="font-size:7.3pt;"><sup>st</sup></span></font> Manifest), complete PAIS implementation, PAIS implemented through METS -> the one chosen
and presenter. Places for the different PAIS elements:</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div>sip Global Info -> digital provenance info</div>
<div>sipTransferObject, sipTransferObjectGroup, sipDataObject -> technical MD (amdsec)</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><b>A=>(all)</b>: send comments on the proposed implementation, and other material sent by BnF.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font size="4"><span style="font-size:14pt;"><b>3</b><b> </b><b>DEDSL XML schema</b></span></font></div>
<div>Planning sent by Daniele yesterday validated by the group.</div>
<div>DB will finalize the project on the CWE framework with resources (NASA to be added as contributor).</div>
<div>The idea is to have a first document for next meeting.<font size="4"><span style="font-size:14pt;"><b> </b></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font size="4"><span style="font-size:14pt;"><b>4</b><b> </b><b>Corot Test case</b></span></font></div>
<div>Not discussed, but updated descriptors and SIPs sent by SM to DB today.</div>
<div>DB will test these files with the tools.</div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font size="4"><span style="font-size:14pt;"><b>Actions review</b></span></font></div>
<div> </div>
<div>Updated actions will be sent separately by JG.</div>
<div> </div>
<div><font size="4" color="red"><span style="font-size:14pt;"><b>End of </b><b>9</b><font size="1"><span style="font-size:6.3pt;"><b><sup>th</sup></b></span></font><b> December meeting minutes</b></span></font></div>
<div>___________________________________________________________________________________________________________</div>
<div><font size="4" color="red"><span style="font-size:14pt;"><b>Part of historical minutes to be reminded </b><font face="Times New Roman" size="3" color="black"><span style="font-size:12pt;">(slightly updated the 9</span></font><font face="Times New Roman" size="1" color="black"><span style="font-size:5.3pt;"><sup>th</sup></span></font><font face="Times New Roman" size="3" color="black"><span style="font-size:12pt;">
Januaru 2015)</span></font></span></font></div>
<div>__________________________________________________________________________________________________________</div>
<div> 2. <b><u>GREEN BOOK</u></b></div>
<div> </div>
<div> <b>2.2 </b><b><u>Core document</u></b></div>
<div> </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> </div>
<div>« open » enumeration technique is cumbersome (TBC)</div>
<div> </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> </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><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> </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> </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> </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> </div>
<div>=> D – (DS) The rightmost column of the table in §4.6.4 shall be renamed « Restriction » instead of « Content »</div>
<div> </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> </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> </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> </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> </div>
<div>=> D – (JG) these XSD shall be placed side to the originals.</div>
<div> </div>
<div>SM: The problem is similar to other GB resources as the use case descriptors or the software prototypes.</div>
<div> </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> </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> </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> <font color="red"> </font></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>___________________________________________________________________________________________________________</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>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><font color="#1F497D">____________________________________________________________________________________________</font></div>
<div> </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>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
</span></font>
</body>
</html>