[Moims-dai] RE: [Moims-rac] DRAFT report to e-ARK on IP design

[David Giaretta]

Hi 

 

@John – yes your comments are valuable  so it would be a good idea to send them before the deadline.

 

@Don – I’ll send an addendum making that offer.

 

Regards

 

..David 

 

From: moims-dai-bounces at mailman.ccsds.org [mailto:moims-dai-bounces at mailman.ccsds.org] On Behalf Of John Garrett
Sent: 15 February 2016 06:46
To: 'MOIMS-Data Archive Ingestion' <moims-dai at mailman.ccsds.org>
Cc: 'D or C Sawyer' <Sawyer at acm.org>; 'David Giaretta' <david at giaretta.org>
Subject: [Moims-dai] RE: [Moims-rac] DRAFT report to e-ARK on IP design

 

Hi,

 

I think the proposed response is very good.

Going through the document,  I made some other comments that are not necessarily related to CCSDS and OAIS.  I’ve attached them if others want to see them.  

I can send the file as separate from our group’s response.

 

I have some family here this weekend so I’m unsure if I’ll make the meeting later this morning.

 

Wishing you prosperity and peace,

-JOhn

 

From: moims-rac-bounces at mailman.ccsds.org <mailto:moims-rac-bounces at mailman.ccsds.org>  [mailto:moims-rac-bounces at mailman.ccsds.org] On Behalf Of bambacher at verizon.net <mailto:bambacher at verizon.net> 
Sent: Wednesday, February 10, 2016 9:44 AM
To: moims-rac at mailman.ccsds.org <mailto:moims-rac at mailman.ccsds.org> 
Subject: Re: [Moims-rac] DRAFT report to e-ARK on IP design

 

David,

This looks good.  Perhaps you could expand your closing sentence to explicitly indicate a willingness/desire to discuss the issues with them. If they have trouble understanding your comments, verbal discussion helps clarify OAIS principles.  It also would allow you ro emphasize the point of the need to not "talk the Talk" but also to "walk the walk" and truly implement OAIS, not just incorporate the jargon.

 

 

On 02/09/16, David Giaretta<david at giaretta.org <mailto:david at giaretta.org> > wrote:

 

Dear all

 

I drafted the following comment on the e-Ark draft common package specification http://www.eark-project.com/news/46-commonspecreleased 

 

What do you think?

 

…David

 

Dear e-ARK

 

I read your deliverable “Introduction to the Common Specification for Information Packages in the E-ARK project” version 0.13 (http://www.eark-project.com/resources/specificationdocs/50-draftcommonspec-1/file )with interest. However, I found a few points which I felt I should comment on.

 

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:

 



 

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.

 

Representation Information is further illustrated in OAIS as follows



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.

 

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.

 

In a similar way I was surprised that there was no reference to all the elements of PDI, such as Provenance Information.

 

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.

 

I look forward to your response.

 

 

 

  _____  


_______________________________________________
Moims-rac mailing list
Moims-rac at mailman.ccsds.org <mailto:Moims-rac at mailman.ccsds.org> 
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-rac

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20160215/7e2b4c91/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 5332 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20160215/7e2b4c91/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 5400 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20160215/7e2b4c91/attachment-0001.jpg>