<font size=2 face="Arial">Daniele,</font>
<br>
<br><font size=2 face="Arial">as suggestion for the book name I suggest
something sharp that allow to grasp the content of the book from the title.
Foe instance</font>
<br>
<ul>
<li><font size=2 face="Arial">Lifecycle for Long Term Data Preservation</font>
<li><font size=2 face="Arial">Long Term Data Preservation Lifecycle</font>
<li><font size=2 face="Arial">Data Management for Long Term Preservation</font></ul>
<br><font size=2 face="Arial">Just a couple of ideas. I see that the term
"Long Term Data Preservation" it is very much used in the community
and I am proposing to capitalise on that. </font>
<br>
<br><font size=2 face="Arial">Regards,</font>
<br>
<br><font size=2 face="Arial">__Mario</font>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Boucon Daniele"
<Daniele.Boucon@cnes.fr></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Mike Martin"
<tahoe_mike@sbcglobal.net>, "garrett@his.com" <garrett@his.com>,
"sawyer@acm.org" <sawyer@acm.org>, "rdowns@ciesin.columbia.edu"
<rdowns@ciesin.columbia.edu>, "esther.conway@stfc.ac.uk"
<esther.conway@stfc.ac.uk>, "david.giaretta@stfc.ac.uk"
<david.giaretta@stfc.ac.uk>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"moims-dai@mailman.ccsds.org"
<moims-dai@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">19/08/2015 20:04</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Moims-dai]
ILF, topics, activities and planning</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">moims-dai-bounces@mailman.ccsds.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Hi all,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Please find below my analysis, and proposed
set of phases by end of the year.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Thank you very much Mike and David for
your material.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b><u>=>First: general feeling:</u></b></font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">1.I’m ok with your last email’s Mike
(format). Furthermore, the EXCEL sheet on activities shows that terms and
points of views differ, but we have points of intersection. The differences
in the main phases are also major.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">2.Thank you David for your last email on
the need for annex: we need indeed an annex describing the relationships
with other community standards such as LTDP.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">3.I’m also in favour to add a section
or annex explaining the relationships with the other standards OAIS, PAIMAS/PAIS
showing the place of this one.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">4.Following different exchanges with Mario
Merri (quotation “</font><font size=2 face="Arial">can't we change the
name of Information Curation Process to something more meaningful?”)</font><font size=2 face="Calibri">,
LOTAR … the term “curation” seems hard to understand. The title may
be decided at the end, but the use of terminology not. I suggest that we
try to find something different.</font>
<br><font size=2 face="Calibri">Something like: “Information Lifecycle
and Long term usage”, “Information usage over its Lifecycle” …</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Crucial terms: lifecycle, data usage, data
management</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">5.Generally speaking, we should be careful
with the terminology (use of metadata …), and keep the coherence with
the OAIS, and keep consistency between them.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b><u>=>Second: structure of the ILF
document</u></b></font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">1.Information Topics vs activities</font>
<br><font size=2 face="Calibri">This issue has been discussed at length.
My feeling is that both may be present, with a focus on information to
be gathered as decided. I’d like to keep a list of main activities as
proposed in section 3.1</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Section 3: the lifecycle framework: the
main stages and information to be gathered</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Section 3.1 Information Lifecycle stages</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">I’m fully ok with this. Why not include
here the detailed description of the phases (sections 3.3.1 till 3.3.4).</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Section 3.2: Information topics</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Section 3.3 Staged curation information
-> change “curation”</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Non normative annex: from David: “</font><font size=2 color=#004080 face="Calibri">non-normative
annexes which map the terminology to existing practice. The obvious one
is the ESA-LTDP work. Being non-normative it should not cause too much
controversy. “</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Non normative annex: schema showing ILF
and other CCSDS archiving standards + relationships</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b><u>=>Third: Comments on Topics</u></b></font>
<br><font size=2 face="Calibri">The existing draft list proposed by David
contains different levels of topics in my opinion.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">David, is there a particular order in the
table of topics?</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">For example: </font>
<br><font size=2 face="Calibri">Some topics deal with categories of info
(e.g. Data, Rep Info, Provenance, SIP, but OAIS “context” does not appear),
others deal with characteristics of Data (e.g Discoverability), others
with transfer of responsibility (handover).</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">We also have to check the list of associated
issues:</font>
<br><font size=2 face="Calibri">For example how about having “Designated
community” in “Data topic” instead of “handover topic”, as this community
uses the data during Operation and Exploitation stages.</font>
<br><font size=2 face="Calibri">How about having the preservation objectives
in the proposal topic?</font>
<br><font size=2 face="Calibri">Catalog could be used in “discoverability
topic” …</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">One of the first tasks we have is to consolidate
this list.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b><u>=>Fourth: activities</u></b></font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">We have to find a way to express link between
the lifecycle stages and associated preservation activities with the topics,
and to consolidate the “typical activities”. Keeping our strategy, we
don’t need to say a lot.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b><u>=>Fifth: Proposal for a set of
phases to produce the ILF standard</u></b></font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">September: Consolidate the list of topics
and consolidate the typical activities</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Till mid-October: High level links between
activities and topics</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Mid October-end November: Develop the topics</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">December: Link with CCSDS archiving standards,
Mapping with LTDP, Internal review</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">What do you think?</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Best regards,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Daniele</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font><tt><font size=2>_______________________________________________<br>
Moims-dai mailing list<br>
Moims-dai@mailman.ccsds.org<br>
</font></tt><a href="http://mailman.ccsds.org/mailman/listinfo/moims-dai"><tt><font size=2>http://mailman.ccsds.org/mailman/listinfo/moims-dai</font></tt></a><tt><font size=2><br>
</font></tt>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>