<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 enclosed, for your validation, the last version of the ESA SAFE test case, including the comments from Mike included in the Minutes dated the 14<font size="1"><span style="font-size:7.3pt;"><sup>th</sup></span></font> August (also duplicated
at the end of this mail).</div>
<div> </div>
<div>To be discussed during our tomorrow telecon.</div>
<div> </div>
<div>Cheers,</div>
<div> </div>
<div>Daniele</div>
<div>____________________________________________________________________</div>
<div><font size="2"><span style="font-size:9pt;">Extract from the 14<font size="1"><span style="font-size:6pt;"><sup>th</sup></span></font> August minutes</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<ol style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;"><b>Comments on the SAFE green book section (from emails MM 22</b><font size="1"><span style="font-size:6pt;"><b><sup>nd</sup></b></span></font><b> July, DB 13</b><font size="1"><span style="font-size:6pt;"><b><sup>th</sup></b></span></font><b>
August).</b></li></span></font>
</ol>
<ol style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">MM: Might want to include a url for SAFE documentation.</li></span></font>
</ol>
<div><font size="2"><span style="font-size:9pt;">DB: agreement on:</span></font></div>
<div><font size="2"><span style="font-size:9pt;">“SAFE (Standard Archive Format for Europe, <span style="background-color:yellow;">see</span> <span style="background-color:yellow;">reference [X]</span> ) is an Earth Observation data archiving format standardized
through the efforts of several European national, institutional and industrial space stakeholders. It aims at covering the role of OAIS AIP”</span></font></div>
<div><font size="2" color="#548DD4"><span style="font-size:9pt;"> </span></font></div>
<ul style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;"><b><u>Action DB:</u></b> ask ESA for the reference to the SAFE 2.0 standard documentation.</li></span></font>
</ul>
<ol start="2" style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">MM: E1 first paragraph, I don't think many people will understand the second sentence. "It aims ..." AIP should be spelled out. Maybe something like "It provides a specification for the organization and content
of an OAIS compatible archive information package."</li></span></font>
</ol>
<div><font size="2"><span style="font-size:9pt;">DB: ok, with the exact meaning “Archival Information Package (AIP)“</span></font></div>
<ol start="3" style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">MM: E1 second paragraph, "These data are from the European Remote Sensing Satellite (ERS) Synthetic Aperture Radar (SAR)."</li></span></font>
</ol>
<div><font size="2"><span style="font-size:9pt;">DB: change to "These data are samples and subset from the European Remote Sensing Satellite (ERS) Synthetic Aperture Radar (SAR), and tailored for the scope of this test case."</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div style="text-indent:35.4pt;"><font size="2"><span style="font-size:9pt;">4. MM: E1 third paragraph. "In the context of this use case," is kind of complicated. How about "In this use case" instead. Also, 'submission to an archive" instead of "submission
into". "The approach followed in this tutorial intends to show the possibility of:" should be "This tutorial illustrates".</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2"><span style="font-size:9pt;">DB: agree with these proposals.</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2"><span style="font-size:9pt;">MM: As you can see, I am finding grammatical issues with every single paragraph. Someone needs to carefully edit all the text in this section, but I don't have time to do in now.</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<ul style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;"><b><u>Action all (at the end)</u></b>: overall reading of the document (consistency, coherence, grammatical issues, …)</li></span></font>
</ul>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<ol start="5" style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">MM: The diagram Figure E-4 shows the three sub-collections of the root collection. I would expect to see a relation-association in the root that "contains" each of these sub collections.? So I guess the arrows
in the figures are generated by the parentCollection specification in each child collection.</li></span></font>
</ol>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2"><span style="font-size:9pt;">DB: (not sure I correctly understand the issue). You’re right: In the CNES tool, the plain arrows are designed from the root towards the leaves, while actually the link in the XML files are specified into the
sub collections or the leaves towards the parent element (the element “parentCollection”).</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2"><span style="font-size:9pt;">MM: I brought this issue of downward and upward pointers or associations up in our discussions last year and Stephane seemed to think the upward pointers were the appropriate ones. I am concerned that having
two ways of specifying the same thing may be dangerous. Anyway, I think there should be some guidance on this issue. The question is: why does Don include "contains" associations from the root collection to the transfer objects in his example when Daniele
doesn't include them between the collection and sub collections in her example?</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2"><span style="font-size:9pt;">DB: the “contains” association (“relationType) is not mandatory at all. I guess it is for better description and understanding. The “parentCollection = NASA_ESA_CNES_Test_Data_Exchange_02” in the Transfer Object
is sufficient to explain the parent-child relationships between both nodes.</span></font></div>
<div><font size="2"><span style="font-size:9pt;">That’s why in the ESA SAFE case this association has not been put over the parent-child relationship.</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<ol start="6" style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">MM: Why are the relations in the SAFE test case at the dataObject level and not at the transfer object level as they are in the ISEE test case?</li></span></font>
</ol>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2"><span style="font-size:9pt;">DB: Up to the Producer and Archive to decide what makes sense.</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2"><span style="font-size:9pt;">In the “Simple case” where there are 4 group types, the association is described from the exact data object inside the right group type.</span></font></div>
<div><font size="2"><span style="font-size:9pt;">In the “Detailed case”, the association could have been drawn from the Transfer Object, because there is only one group type and one data object inside. The choice of the data object as source of the association
is to draw the parallel between simple and detailed case. In this case, both descriptions are possible.</span></font></div>
<div><font size="2" color="#548DD4"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2" color="#548DD4"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2"><span style="font-size:9pt;">Discussion on “open” possibilities in the standard, such as the way to express associations.</span></font></div>
<div><font size="2"><span style="font-size:9pt;">MM: informal expression of elements in the MOT -> practical use?</span></font></div>
<div><font size="2"><span style="font-size:9pt;">DS: different ways to model the same situation -> not easy to understand.</span></font></div>
<div><font size="2"><span style="font-size:9pt;">DS: Try to normalize the diagram?</span></font></div>
<div><font size="2"><span style="font-size:9pt;">MM: make the documentation clearer.</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<ol start="7" style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">MM: Why are the groupTypeStructureName entries "SET" in the simple case and "Directory" in the detailed case?</li></span></font>
</ol>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div><font size="2"><span style="font-size:9pt;">DB: In both cases the “physical” high level group for the products on the Producer side is a directory and could have been viewed as “directory” “EO_PRODUCTS”. In fact this level has not been modeled. So in
the simple case we have a group (mandatory) of one zip file that is the product itself -> viewed as a “set”, in the detailed case we have a group (mandatory) of one directory that is the product itself containing different files -> viewed as a “directory”.</span></font></div>
<div><font size="2"><span style="font-size:9pt;"> </span></font></div>
<div style="text-indent:18pt;"><font size="2"><span style="font-size:9pt;">DS: give more explanation in the tutorial (see point 2 below). </span></font></div>
<div style="text-indent:18pt;"><font size="2"><span style="font-size:9pt;"> </span></font></div>
<ul style="margin:0;">
<font size="2"><span style="font-size:9pt;">
<li style="margin-top:5pt;margin-bottom:5pt;"><b><u>Action DB:</u></b> give explanation on the reason why using group structure name = “directory” in the detailed case, and “set” in the simple case (from Minutes 14<font size="1"><span style="font-size:6pt;"><sup>th</sup></span></font>
August).</li><li style="margin-top:5pt;margin-bottom:5pt;"><b><u>Action DB:</u></b> updated version of the ESA SAFE test case with comments from the 14<font size="1"><span style="font-size:6pt;"><sup>th</sup></span></font> August telecon.</li></span></font>
</ul>
<div><font size="2"><span style="font-size:9pt;">______________________________________________________________</span></font></div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>