<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:10.0pt;
font-family:"Arial","sans-serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"Préformaté HTML Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:Consolas;
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:10.0pt;
font-family:"Arial","sans-serif";
color:black;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
{mso-style-name:"HTML Preformatted";
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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 bgcolor="white" lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi David and all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The idea to have short list is ok for me, if the content remains as previously defined (items expanded in David’s list), that is I think the case.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">David, what in your point of view should be added –or cut- to cover small data creation projects?<o:p></o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I agree that we need to highlight how and when the information is collected (this is independent from the list of topics itself we want to agree
on now).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Daniele<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">De :</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> david.giaretta@stfc.ac.uk [mailto:david.giaretta@stfc.ac.uk]
<br>
<b>Envoyé :</b> jeudi 24 septembre 2015 08:25<br>
<b>À :</b> tahoe_mike@sbcglobal.net; Boucon Daniele<br>
<b>Cc :</b> garrett@his.com; Sawyer@acm.org; rdowns@ciesin.columbia.edu; esther.conway@stfc.ac.uk; moims-dai@mailman.ccsds.org; stephane.reecht@bnf.fr<br>
<b>Objet :</b> RE: Possible scope reduction<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">Dear all<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">I’m not sure I’ll be able to join the call today so I thought I should contribute my view by email.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">I think the proposal to cut things down is largely based on a “big project” point of view.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">My understanding was that we needed to cover both large and small data creation projects.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">Of course we need to map to AIP components because that is what is needed for long term preservation, and that is what
all the topic lists have at their core. However we also need to look as how and when the information is collected and also how the data creators can provide information that will help/encourage the re-use and adding value to the data.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">…David<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"></a><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext"> Mike Martin [<a href="mailto:tahoe_mike@sbcglobal.net">mailto:tahoe_mike@sbcglobal.net</a>]
<br>
<b>Sent:</b> 22 September 2015 16:39<br>
<b>To:</b> Boucon Daniele <<a href="mailto:Daniele.Boucon@cnes.fr">Daniele.Boucon@cnes.fr</a>><br>
<b>Cc:</b> John Garrett <<a href="mailto:garrett@his.com">garrett@his.com</a>>; Giaretta, David (STFC,RAL,RALSP) <<a href="mailto:david.giaretta@stfc.ac.uk">david.giaretta@stfc.ac.uk</a>>;
<a href="mailto:Sawyer@acm.org">Sawyer@acm.org</a>; <a href="mailto:rdowns@ciesin.columbia.edu">
rdowns@ciesin.columbia.edu</a>; Conway, Esther (STFC,RAL,RALSP) <<a href="mailto:esther.conway@stfc.ac.uk">esther.conway@stfc.ac.uk</a>>;
<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>; <a href="mailto:stephane.reecht@bnf.fr">
stephane.reecht@bnf.fr</a><br>
<b>Subject:</b> Re: Possible scope reduction<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB">Hi Daniele and others<br>
<br>
Overall I think our goal should be to get the topic/issue list down to about 10 topics, otherwise this will be too complicated for us to work on and too complicated for anyone to read. I have included a modified version of my spreadsheet where I have tried
to show how your topic list correlates to my list. Here is some discussion.<br>
<br>
1. My thoughts was that line 9, Data Inventory... was included in my line 4 "What types of data (raw, processed etc) will be produced, and the total volume of data which will be produced. What is the schedule for major project milestones and deliveries to
the archive."<br>
<br>
2. Line 5, 6, 11, 13, 14, 15, 17 and 27 all deal with standards for and descriptions of data and metadata. I think we need a cleaner way of dealing with these topics. That's why I suggested we focus on the diagram that describes the components of the AIP.
The topics in the diagram include:<br>
<br>
Data and Representation Info:<br>
digital object<br>
structure information <br>
semantic information<br>
other representation information<br>
PDI:<br>
reference information<br>
provenance information<br>
context information<br>
fixity information<br>
access rights information<br>
Packaging:<br>
packaging information<br>
package description<br>
<br>
So I was thinking maybe we would have one topic that covered all the components of the AIP, with subtopics for all the components. Or maybe it would be better to have three topics, Data and RI, PDI and Packaging.<br>
<br>
3. I included my line 10 "What special products need to be created..." to try to cover your line 23, 24, 25. However, I really think all those topics discuss things that need to be included in AIP components.
<br>
<br>
4. My line 11 "Processing Workflow" would encompass your lines 12, 29, 34. This topic could be included in the AIP components discussion.<br>
<br>
5. My line 12 "Inputs, parameters..." would encompass your line 7 and 37. This topic could be included in the AIP components discussion.<br>
<br>
6. My line 17 "How will the deliveries be packaged" covers your line 41 "handover - pointers to the components to be transferred.<br>
<br>
7. If we are focusing on what the data provider must do during the lifecycle then I don't see how your line 26 or 43 relate to this document. They seem to be internal archive issues.<br>
<br>
8. I put line 49 on the list, but now I don't think we have the resources to go into that topic.<br>
<br>
Looking at my list, I also think that 13 "What calibration and system test tools and data will be delivered" and 14 "Provide a bibleography...", 15 "How do we verify...", 18 "Who is the owner" should be incorporated in the AIP topic or topics discussion.<br>
<br>
Thanks, Mike<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial","sans-serif"">On 9/18/2015 3:24 AM, Boucon Daniele wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span lang="EN-GB">Hi Mike and all,<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">As only John and myself responded to move the today ILF telecon, I suggest that we keep a short slot, and we can plan another one in a short delay.<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">Here are my comments on Mike's proposal: <o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">1. I find that the mapping you propose between the life cycle activity and the topics interesting.<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">2. I find your point of view in the Info life cycles stage interesting. If we adopt <o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">Gathering the lines are ok, considering the fact that they will be expanded in sub bullets.<o:p></o:p></span></pre>
<pre><span lang="EN-GB">I'm not convinced that we have to cut the exploitation part.<o:p></o:p></span></pre>
<pre><span lang="EN-GB">I'm in favour of keeping the "adding value" and "discoverability", as this is what is a great interest for the users.<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">The lines from David's table-topicsand subtopicsDB- that I have not found in Mike's table are the following:<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">Line 5: Data Semantics of the data elements repInfo? Needed to support interpretation and interoperability<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 6: Data Context documentation Context Ex: description of mission, instrument, .<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 7: Data Quality specifications ?? DI ?? Future confidence in data. Definition of quality parameters. Ex: QA4EO . => related to quality parameters, could ne enlarged in Mike's proposal<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 9: Data Inventory of data produced/expected What level of granularity is needed? List of info + relationships among all the info (network)<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 11: Representation Information Applicable standards RepInfo Complex topic, maybe too big for general document<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 12: Representation Information Software dependencies RepInfo Minimize as archives don't have resources to maintain software<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 13: Representation Information Data dictionaries and other semantics RepInfo Need clean mechanism to transfer to archive, support interoperability<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 14: Representation Information Format definitions and formal descriptions RepInfo Needed to provide access to data.<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 15: Representation Information Information Model RepInfo Information Model includes relationships between classes - important for automated production, validation, sw development<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 17: Descriptive Information Outline of background concepts needed to understand the project Descriptive Info Needed for future use of the data.<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 23: (Adding) value Related data which may in the future be combined with this data This may be too broad. <o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 24; (Adding) value Other software which may be used on the data Tutorials are very valuable for future access to the data.<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 25: (Adding) value Interfaces that are applicable to the data e.g. images, tables. I don't understand this issue.<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 26: (Adding) value Potential value of the data and likely business case for sustainability Archive Support Plan <o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 27: Proposal Record of origins of the project e.g. in a CRIS system Context Descriptive information, record of commitments, evaluation of project success<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 29: Provenance Documentation about the hardware and software used to create the data, including a history of the changes in these over time Provenance How do we capture this?<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 34: Provenance Record of any special hardware needed Provenance Submission Agreement?<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 37: Authenticity Who was responsible for each stage of processing To allow archive to contact preparer? Not generally collected.<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 41: Handover Pointers to the components to be transferred to the archive How does this differ from inventory in Data Topic<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 43: Handover Potential preservation aims of the archive Part of Archive Support Plan<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Line 49: Handover Resident Archives Intermediary between provider and archive in some cases for maintaining specialized h/w or s/w.<o:p></o:p></span></pre>
<pre><span lang="EN-GB"> <o:p></o:p></span></pre>
<pre><span lang="EN-GB">Mike, could you please tell me if this analysis is correct or not? Are some of them included in other lines of your table?<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">As an aim for our telecon, I suggest that we all give opinion on this list (grouping, what more to include or expand).<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">Regards,<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">Daniele<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">-----Message d'origine-----<o:p></o:p></span></pre>
<pre><span lang="EN-GB">De : Mike Martin [<a href="mailto:tahoe_mike@sbcglobal.net">mailto:tahoe_mike@sbcglobal.net</a>] <o:p></o:p></span></pre>
<pre><span lang="EN-GB">Envoyé : mercredi 16 septembre 2015 15:32<o:p></o:p></span></pre>
<pre><span lang="EN-GB">À : Boucon Daniele<o:p></o:p></span></pre>
<pre><span lang="EN-GB">Cc : John Garrett; <a href="mailto:david.giaretta@stfc.ac.uk">david.giaretta@stfc.ac.uk</a>; <a href="mailto:Sawyer@acm.org">Sawyer@acm.org</a>; <a href="mailto:rdowns@ciesin.columbia.edu">rdowns@ciesin.columbia.edu</a>; <a href="mailto:esther.conway@stfc.ac.uk">esther.conway@stfc.ac.uk</a>; <a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a><o:p></o:p></span></pre>
<pre><span lang="EN-GB">Objet : Possible scope reduction<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">Hi everyone<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">If you haven't started looking at the attachments here are two slightly edited versions.<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">Thanks, Mike<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
</blockquote>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
</div>
</body>
</html>