<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi David,<br>
I'm not at all proposing to extend the scope, just shift the
focus. I'm concerned that the title leads one to expect a
discussion of information or data lifecycle management while the
body of the document is focused on the project transitions,
packaged as a sequence representing a project lifecycle. <br>
<br>
I wanted to re-orient that focus on data/information use
transitions. Data is put to differing uses over time, and a data
lifecycle is intended to illustrate that. <br>
<br>
I agree with Don that my focus on Designated Community may have
been a too strong. Mentioning it as a constituent of the
preparation to transfer to an Archive (I've labeled that part as
Curation and Disposition, which I also agree are outside of the
scope of this document) should be considered. I don't think it
wrong however to show the data lifecycle's inclusion of an OAIS
representative archive as the termination of the project data
lifecycle.<br>
<br>
Terry<br>
<br>
On 3/15/2016 5:36 AM, David Giaretta wrote:<br>
</div>
<blockquote cite="mid:003701d17e9e$187a8430$496f8c90$@giaretta.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 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;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:13.5pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Calibri Light",sans-serif;
color:#1F4D78;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">Hi
Terry<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">I
would be concerned if you are proposing to extend the scope
of the document to overlap with what OAIS and PAIS/PAIMAS do
perfectly adequately.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">Besides
somehow resolving that overlap this would mean that we would
need to find a great deal more effort from somewhere to
finish the document in a reasonable time.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US">..David<o:p></o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"
lang="EN-US">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"
lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:moims-dai-bounces@mailman.ccsds.org">moims-dai-bounces@mailman.ccsds.org</a>
[<a class="moz-txt-link-freetext" href="mailto:moims-dai-bounces@mailman.ccsds.org">mailto:moims-dai-bounces@mailman.ccsds.org</a>] <b>On
Behalf Of </b>terry.longstreth<br>
<b>Sent:</b> 23 February 2016 16:06<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a> >>
MOIMS-Data Archive Ingestion
<a class="moz-txt-link-rfc2396E" href="mailto:moims-dai@mailman.ccsds.org"><moims-dai@mailman.ccsds.org></a><br>
<b>Subject:</b> [Moims-dai] Information or data
lifecycle vs Project lifecycle - incomplete monograph<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">I've been
searching for a way to articulate my concerns with the
Lifecycle document, and still haven't found it; the way to
articulate it, I mean. <br>
<br>
So, I'll just charge ahead. I don't think these ideas can be
of much effect on the document itself, since I'm so late to
the party, but perhaps by putting it in front of the group,
others can make better use of them than I. <br>
<br>
I'm concerned that we are serving two masters without
recognizing the driving and not necessarily congruent
interests of those two:<br>
<br>
First, we've been told that the impetus for the 'lifecycle'
document came from work items or expected tasking in contracts
where the <b>contracting agency </b>wanted to ensure that
they could, with confidence, be assured that all relevant data
related to a funded activity would be available for them to
review and reuse. <br>
<br>
Second, I've an internal (institutional) bias, which I believe
I share with those on this list, toward supporting the goal
of meeting the needs of the <b>Designated Community</b>,
which may be but probably isn't the same as the contracting
agency. <br>
<br>
Now, the purpose and body of the Lifecycle document is clearly
slanted toward the first constituency. For example, the
lifecycle elements are, as already noted by Don, John, and
several others, more typical of a project lifecycle than a
data or information lifecycle. I had accepted an action to
review and offer suggestions to improve Chapter 5 and it's
associated table. I propose that the table should be recast to
more properly reflect a Generic Data Lifecycle that
accommodates longterm, potentially unending, data generation
environments as well as situations where data lifecycle
management is associated with and punctuated by short-term
project level goals. The generic data lifecycle emphasizes
the data operations leading from initial or conceptual
planning for data collection or generation, through to
explicit freezing of a data package and final disposition. <o:p></o:p></p>
<h3>Generic Data Lifecycle<o:p></o:p></h3>
<p class="MsoNormal">Conceptualization->Origination->Availment->Processing->Packaging->Curation
and Disposition<o:p></o:p></p>
<div>
<p class="MsoNormal">-- <br>
<img style="width:3.5347in;height:1.4791in"
id="_x0000_i1025"
src="cid:part2.09050903.09000405@comcast.net" height="142"
width="339"><o:p></o:p></p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Moims-dai mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Moims-dai@mailman.ccsds.org">Moims-dai@mailman.ccsds.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.ccsds.org/mailman/listinfo/moims-dai">http://mailman.ccsds.org/mailman/listinfo/moims-dai</a>
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<img src="cid:part3.03060904.01070305@comcast.net" border="0"></div>
</body>
</html>