<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><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:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
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;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@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 lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Dear all<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I drafted the following comment on the e-Ark draft common package specification <a href="http://www.eark-project.com/news/46-commonspecreleased">http://www.eark-project.com/news/46-commonspecreleased</a> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What do you think?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>…David<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dear e-ARK<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I read your deliverable “Introduction to the Common Specification for Information Packages in the E-ARK project” version 0.13 (<a href="http://www.eark-project.com/resources/specificationdocs/50-draftcommonspec-1/file">http://www.eark-project.com/resources/specificationdocs/50-draftcommonspec-1/file</a> )with interest. However, I found a few points which I felt I should comment on.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>You describe, in section 1.1 “Common Specification and OAIS Information Packages” the 3 types of Information Packages which OAIS describes. However, you fail to describe the basic (general) definition of an Information Package, which is shown as:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='mso-fareast-language:EN-GB'><img border=0 width=900 height=468 id="Picture_x0020_1" src="cid:image003.png@01D16285.13A41D70"></span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The Content Information has both the Data Object and the associated Representation Information. Preservation Description Information as Reference Information, Provenance Information, Context Information, Access Rights Information and Fixity Information. As indicated in the diagram the only required element is Packaging Information – because that allows one to “open” the package. The AIP is specified much more definitively since all the elements must be present.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Representation Information is further illustrated in OAIS as follows<o:p></o:p></p><p class=MsoNormal><span style='mso-fareast-language:EN-GB'><img border=0 width=868 height=495 id="Picture_x0020_2" src="cid:image005.png@01D16285.13A41D70"></span><o:p></o:p></p><p class=MsoNormal>I was surprised to note that there is no reference to Representation Information, and little reference to Semantic (Representation) Information and no mention of things related to “Other (Representation) Information” such as software. There is mention of “software which has been used to create the package” and “metadata syntax and semantics” and it seems clear these do not refer to the Representation Information of the object of concern.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In order to maintain the association with OAIS I would expect that the relationship to OAIS should be made clearer, in particular showing where the various elements of Representation Information may be found in your proposed structure.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In a similar way I was surprised that there was no reference to all the elements of PDI, such as Provenance Information.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Of course the SIP and DIP need only Packaging Information but the general definition of the package must allow all of the elements, which of course AIPs will definitely need to contain.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I look forward to your response.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>