From david at giaretta.org  Mon Feb  8 15:26:27 2016
From: david at giaretta.org (David Giaretta)
Date: Mon, 8 Feb 2016 15:26:27 -0000
Subject: [Moims-rac] DRAFT report to e-ARK on IP design
Message-ID: <008601d16285$147f8950$3d7e9bf0$@giaretta.org>

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.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/9857a6e3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 97566 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/9857a6e3/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 33464 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/9857a6e3/attachment-0001.png>

From david at giaretta.org  Mon Feb  8 16:06:16 2016
From: david at giaretta.org (David Giaretta)
Date: Mon, 8 Feb 2016 16:06:16 -0000
Subject: [Moims-rac] FW: Request for response.
In-Reply-To: <32351_1454943143_56B8ABA7_32351_1611_1_OFB57E7BE5.95ACBEF0-ONC1257F53.00519728-C1257F53.0051B215@esa.int>
References: <32351_1454943143_56B8ABA7_32351_1611_1_OFB57E7BE5.95ACBEF0-ONC1257F53.00519728-C1257F53.0051B215@esa.int>
Message-ID: <00a001d1628a$a44b1d10$ece15730$@giaretta.org>

 

 

From: Mario.Merri at esa.int [mailto:Mario.Merri at esa.int] 
Sent: 08 February 2016 14:52
To: david at giaretta.org; John Garrett <garrett at his.com>
Subject: RE: Request for response.

 

Another piece of info. 

__Mario 
----- Forwarded by Mario Merri/esoc/ESA on 08/02/2016 15:51 ----- 

From:        "Nick Tongson" <NickT at aiaa.org <mailto:NickT at aiaa.org> > 
To:        "Eduardo W. Bergamini" <e.w.bergamini at uol.com.br
<mailto:e.w.bergamini at uol.com.br> >, "Mario Merri, Dr. - CCSDS CESG MOIMS AD
- ESOC/ESA" <Mario.Merri at esa.int <mailto:Mario.Merri at esa.int> > 
Cc:        "James Afarin, Dr. - Secretary to CCSDS & CMC/CCSDS Ch. & Secr.
to ISO TC20/SC13" <James.Afarin at nasa.gov <mailto:James.Afarin at nasa.gov> >,
"Nestor Peccia, Dr. - Director CESG/CCSDS - ESOC/ESA" <Nestor.Peccia at esa.int
<mailto:Nestor.Peccia at esa.int> > 
Date:        08/02/2016 15:34 
Subject:        RE: Request for response. 

  _____  




Hello Eduardo, 
  
Just a reminder that the letter has two parts. The first part is the
designation by ISO/TC46/SC4 of two observers or liaison representatives from
their side (one is the Chairman of TC46/SC4 and the other an expert). In
accordance with ISO Directives, no decision is needed - we are obligated to
add them. Indeed, they have already been added by ISO Central Secretariat. 
  
The second part is their willingness to welcome an observer or liaison
representative from our side (SC13). This is where Mario and David Giaretta
(MOIMS-DAI WG) come in. However, this is not required. It is up to
SC13/CCSDS if we want to reciprocate and also designate an observer
(TC46/SC4 is also obligated to accept SC13's designation). 
  
Regards, 
  
Nick 
  
Nick Tongson 
Director - Standards 
American Institute of Aeronautics and Astronautics   <http://www.aiaa.org/>
www.aiaa.org           
12700 Sunrise Valley Drive, Suite 200 
Reston, VA 20191-5807
800-639-AIAA (2422) 
 <mailto:nickt at aiaa.org> nickt at aiaa.org 703.264.7515 (direct) 
  
AIAA is co-chairing Engineers Week 2016 with The Boeing Company and SAE
International.  <http://www.aiaa.org/engineersweek/> Celebrate February
21-27! 
 <http://www.discovere.org/our-programs/engineers-week> Engineers Make A
World Of Difference while Shaping the Future of Aerospace! 
  

  
 <https://www.facebook.com/AIAAfan>  <http://www.twitter.com/#!/aiaa>
<http://www.linkedin.com/company/aiaa>
<https://www.youtube.com/channel/UCQUxcIsXCZuwCa34u1J5COw>
<https://instagram.com/aiaaerospace> 
  
From: Eduardo W. Bergamini [ <mailto:e.w.bergamini at uol.com.br>
mailto:e.w.bergamini at uol.com.br] 
Sent: Sunday, February 07, 2016 11:33 AM
To: Mario Merri, Dr. - CCSDS CESG MOIMS AD - ESOC/ESA
Cc: James Afarin, Dr. - Secretary to CCSDS & CMC/CCSDS Ch. & Secr. to ISO
TC20/SC13; Nestor Peccia, Dr. - Director CESG/CCSDS - ESOC/ESA; Nick Tongson
Subject: Request for response. 
  
Dear Mario, 
  
I hope you are fine, indeed. 
  
At this very moment, James Afarin, in Cc., is reviewing the Minutes,
Resolutions 
and Action Items of the ISO TC20/SC13 meeting which was held in Darmstadt,
last 
November. Resulting from the discussions we had in that meeting, where you 
were consulted on the subject, one Resolution and 2 associated Action Items
are 
being proposed for consideration, and they are described in the following
lines: 
  
----- 


SC13-R-2015-11-4 

ISO TC46/SC04 Subcommittee (on Technical interoperability) proposed a
liaison to ISO TC20/SC13. E. Bergamini received a letter of proposal of
liaison from Mrs. Heiskanen. The letter mentions two OBSERVERS from ISO
TC46/SC04 who would serve as liaisons to ISO TC20/SC13. ISO TC20/SC13
decided that Dr. Mario Merri, Area Director MOIMS/CESG/CCSDS, present to
this meeting, would be getting in contact with Dr. David Giaretta, Chairman
of MOIMS Data Archive Ingestion Working Group to determine the interest from
CCSDS-ISO TC20/SC13 to establish a liaison with ISO TC46/SC04 Subcommittee
and, then, consider the nomination of a Liaison. Then, a letter from ISO
TC20/SC13 to ISO TC46/SC04 is be sent answering to the proposal for a
liaison between the two Subcommittees.


----- 
  


SC13-A-2015-11-2 

Request from Dr. Mario Merri, Area Director MOIMS/CESG/CCSDS, his contact
with Dr. David Giaretta, Chairman of MOIMS Data Archive Ingestion Working
Group to determine the possible interest from CCSDS-ISO TC20/SC13 to
establish a liaison with ISO TC46/SC04 (Technical interoperability)
Subcommittee. If there is such an interest, CCSDS MOIMS DAI WG should
nominate a person to act as the liaison of CCSDS-ISO TC20/SC13, in this
case. 
Actionee: Chairman of the Subcommittee 
Due Date: Before the 48th meeting in Brazil 


SC13-A-2015-11-3 

Upon a response from Dr. Mario Merri, the Subcommittee will address an ISO
TC20/SC13 response to ISO TC46/SC04 on the interest to establish a liaison
between both subcommittees. 
Actionee: Chairman and Secretary 
Due Date: Till the 48th meeting, in Brazil


----- 
Also of fundamental importance, enclosed to this current message you find
the 
complete content of the ISO TC20/SC13 - ISO TC46/SC04 correspondence which 
was exchanged so far between them. These enclosed contents are those which 
motivated the related discussions we held in the last SC13 meeting, in
Darmstadt. 
  
In order to speed up the pendence we have in relation to ISO TC46/SC04 
Subcommittee, I wish to ask you to get acquainted with the enclosed 
correspondence and, after your evaluation with Dave Giaretta (MOIMS-DAI WG),

you may express us your joint impression that may provide us with the basis
that 
will orient our pending response to the inquiring Subcommittee. 
  
>From what I could aprehend from the correspondence we received from ISO
TC46/ 
SC04 Subcommittee, it is my personal impression that we can not ignore the 
need of nominating a corresponding (MOIMS-DAI WG originated) liaison person 
from our side. However, the pending response letter that James Afarin and I
would, 
in a 1st. opportunity, be addressing to ISO TC46/SC04 Subcommittee would, 
based on what Dave Giaretta and yourself my tell us, make clear what would
be, 
the expected commitment that could be observed by liaison person from our
side, 
in the context of such a liaison work, after a common understanding is
settled 
between both sides, in that direction. 
  
In view of my last manifest to them, for the time being I feel I owe a short
term, 
simple e-mail response to ISO TC46/SC04, which I plan to address in my 1st. 
opportunity, where I will simply mention them that their kind proposal was 
discussed in our last (Darmstadt) SC13 meeting and that internal actions are

being taken to send them a formal response from ISO TC20/SC13 in our 1st. 
opportunity. 
  
Thank you for your consideration to this current request. We look for your 
answer in a 1st. opportunity. 
  
Please, confirm this message. Thank you. 
  
With my kind regards, 
Eduardo Bergamini 
Chairman ISO TC20/SC13 Subcommittee 
  
ENCLOSURES: 2 
  
Cc. James Afarin, Secretary of ISO TC20/SC13 Subcommittee 

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/4bec9a6d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled attachment 00057.jpg
Type: image/jpeg
Size: 5543 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/4bec9a6d/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled attachment 00060.png
Type: image/png
Size: 2203 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/4bec9a6d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled attachment 00063.png
Type: image/png
Size: 2282 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/4bec9a6d/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled attachment 00066.png
Type: image/png
Size: 2249 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/4bec9a6d/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled attachment 00069.png
Type: image/png
Size: 2442 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/4bec9a6d/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled attachment 00072.png
Type: image/png
Size: 2249 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/4bec9a6d/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled attachment 00075.png
Type: image/png
Size: 2323 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160208/4bec9a6d/attachment-0005.png>

From bambacher at verizon.net  Wed Feb 10 14:44:09 2016
From: bambacher at verizon.net (bambacher at verizon.net)
Date: Wed, 10 Feb 2016 08:44:09 -0600 (CST)
Subject: [Moims-rac] DRAFT report to e-ARK on IP design
Message-ID: <3230254.59899.1455115449072.JavaMail.root@vznit170182.mailsrvcs.net>

An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-rac/attachments/20160210/bda4c458/attachment.html>

From Sawyer at acm.org  Sun Feb 14 20:38:44 2016
From: Sawyer at acm.org (D or C Sawyer)
Date: Sun, 14 Feb 2016 15:38:44 -0500
Subject: [Moims-rac] Re: [Moims-dai] DRAFT report to e-ARK on IP design
In-Reply-To: <008601d16285$147f8950$3d7e9bf0$@giaretta.org>
References: <008601d16285$147f8950$3d7e9bf0$@giaretta.org>
Message-ID: <0EBF6DDA-D36D-4BB6-9FA2-11B7981CBE76@acm.org>

Hi David,

Since they want this ‘Common Specification’ to be applicable to SIPs, AIPs, and DIPs, and since they appear to be identifying what the AIP says is a Content Type, I agree they should be discussing all the elements of an AIP and how they related to their ‘Common Specification’.  They should also relate it to the PAIS specification of a SIP.  Otherwise I like your response.

cheers-
Don
(ps I don’t know that the moims lists are working for my mailing, although I seem to be getting other’s mailings)

On Feb 8, 2016, at 10:26 AM, David Giaretta <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:
>  
> <image003.png>
>  
> 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
> <image005.png>
> 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-dai mailing list
> Moims-dai at mailman.ccsds.org
> http://mailman.ccsds.org/mailman/listinfo/moims-dai