[Moims-dai] Reminder of Skype call Tuesday

Mon Mar 22 18:41:39 UTC 2021

Meeting: 10:00 Tuesday (Washington DC time), but because of Daylight Saving
Time changes the time for the meeting in Europe will be 1400 UK time, 1500
Paris time this week and next week. After that Europe also moves to Daylight
Saving Time and we return to the normal schedule.

If you do not receive a notification from Skype then please join it by
clicking the link:

 <https://join.skype.com/ykyu5SIPhSnD> https://join.skype.com/ykyu5SIPhSnD

*Don't have Skype yet? Download it before you join  <https://www.skype.com>
https://www.skype.com

Draft agenda:

1.	Feedback from MOIMS AD on books  I received the following rapid
response from Marc Duhaze. COMMENTS ADDED (please check, especially the text
proposed)

Hi All,

First of all, Im a newbie in this domain, so please be tolerant ;)

About CCSDS 652.1-M-2-updated : (see
https://www.dropbox.com/s/80xzgt3qpql633k/652x1m2_20210116.doc?dl=0)

*	As it is mainly a clone of the ISO/IEC 17021-1 standard fitted in a
CCSDS template,

*	I have no specific comment, so its fine for me

READY TO  SEND TO AD

About CCSDS 653.0-R-1 : (see
https://www.dropbox.com/s/r2tmotj8ejw5lm0/CCSDS653.0R1-20210322.docx?dl=0)

*	Initial page : reference should be CCSDS 653.0-R-1, no ?

DONE, also changed date to March 2021, but expect CCSDS Editor will make
appropriate changes

*	About Brigitte comment : p3-1 

*	I would have expected a more "in depth" analysis of the project
documentation that should be preserved at each phase.
*	David answer : Yes, specific aspects of the project documentation
will almost certainly be preserved

*	Im not sure about what was expected by Brigitte and so if David
answers the question, however my opinion is that a lot of examples of
possible project documents are given for each step of the collection
group. So I assume that at the end of a phase, all the document produced
during the different steps of a collection group are preserved. So to answer
the Brigitte question, you should perhaps add a sentence in that way, at the
end of §3.2 

Sentence added at section 3.2 Important types of information are identified
in section 4 and a number of checklists are provided in ANNEX C and ANNEX D,
but the variety of potential projects and their documents means that only
general guidelines can be given.

*	About Mario comment : p4-4

*	All information in the PDI are already described in the OAIS book
at high level. In my understanding, the value of this book should be in
going one level down and prescribe, for each PDI, the minimum common
denominator of required information...
*	David answer : The point is that PDI, and in particular Provenance,
is to be collected throughout, rather than left to the end. In OAIS this is
implicit. This document makes it explicit.

*	Im not sure the answer covers the question raised by Mario. Is it
possible to split the information list provided for each type (Reference,
Provenance, Context, 
) into different categories such as  required
information, recommended information, optional information 
 ?

Add paragraph to 4.1.2

Of these the Provenance is likely to be required over the entire life of the
project, and beyond, being relevant to all subsequent outcomes of the
project, and so is always required. Reference, Fixity, Context and Access
Rights Information may not be required through all successive stages, unless
relevant to the Provenance.  

TO BE DISCUSSED

*	I agree with other answers to Mario and Brigitte comments and have
no other comment

OK

About CCSDS 652.0-W(M)-1.1 :  (see
https://www.dropbox.com/s/q8uofeoewdllrrw/652x0w1x1-20210322.doc?dl=0)

*	Page 1-5 : you missed a written : Preservation Strategic Plan: A
written statement
  to change to 
documented statement

DONE

*	About Mario comment : p3-5

*	This seems to me a characteristic of any good work position. I
would remove it from here. By the same token, you could also ask for full
medical coverage for the repository staff, 

*	David answer We disagree. Our experience is that it is worth statin
this metric explicitly.  If one goes down the route you propose we could
remove most metrics

*	Sorry Mario ;) , but I agree with David answer. @Mario, what about
you ?

OK

*	About Brigitte comments p5-1 and 5-11

*       BBh34: besides adapting and changing its hardware and software, it
seems to me that the repository architecture should be designed so that it
can cope with these changes with a minimum of service perturbation (for
instance having dedicated test environment to validate new software release
and to train staff, provide possibilities of roll-back when installing new
version, privilege whenever possible backward compatibility).

If the repository architecture is not correctly dimensioned, any
intervention will lead to more or less important service interruptions.

Consider adding a requirement/metric dedicated to this issue (the
architecture must be designed and dimensioned to meet the preservation
objectives).

*       David answer  It was felt that, while what you write is correct, it
seemed unnecessary to demand that auditors review the overall design of the
archive, but the system requirement/design documents may be presented as
evidence

*	BBh39: cf. BBh34. Prior to that, the repository architecture should
be adequately dimensioned
*	David answer : Metrics covering adequate scaling already in the
document

*	To me, the points raised by Brigitte are covered by exiting
requirements in the document such as 

*	The repository shall identify and manage the risks to its
preservation operations and goals associated with system infrastructure.
*	The repository shall have adequate hardware and software support
for backup functionality sufficient for maintaining the system support to
preserve the repository content and tracking repository functions.   

*	I agree with other answers to Mario and Brigitte comments and have
no other comment

OK

Regards.

Marc.

2.	OAIS  please add comments to OPEN OAIS RIDS, especially about DOI
and FAIR. It would be good to close these to the point of asking for being
able to ask for the agreement of the submitter.

Suggested Disposition

312 <http://review.oais.info/show_bug.cgi?id=312> 

OAIS Jun

Section 

A

Consider updating text about existing archives.

NO CHANGE

Do not put anything in

322 <http://review.oais.info/show_bug.cgi?id=322>  

OAIS Jun 

Section 

2 

		Clarify usefulness of OAIS for Interoperability,
re-reproducibility and re-use  <http://review.oais.info/show_bug.cgi?id=322>

The requirements for preservation are also important for current use of
information. This change will make that point clearer. 

CHANGE PROPOSED

325 <http://review.oais.info/show_bug.cgi?id=325>  

OAIS Jun 

Section: 

9 

		NASA/JSC 1 Only one set of access rights per data object
<http://review.oais.info/show_bug.cgi?id=325> 

Access control enforcement will be greatly simplified. 

CHANGE PROPOSED

326 <http://review.oais.info/show_bug.cgi?id=326>  

OAIS Jun 

Section: 

2 

		INPE-1:Detailed review be made of Figure A-1 in page A-2 in
order that it may guaranteed that the functionally that it represents
-fully- corresponds to the naturally more detailed functionality that is
represented in the set of Figures 4-2 through 4-7.
<http://review.oais.info/show_bug.cgi?id=326> 

he author of this proposal, for transforming it in a Brazilian Standard
(ABNT/BR) had to translate to the Portuguese the previous OAIS document ISO
14721:2012, which contains the document CCSDS 650.0-M-2. The proposal being
made in this current RID ha... 

NO CHANGE

Response has been proposed

327 <http://review.oais.info/show_bug.cgi?id=327>  

OAIS Jun 

Section 

1 

		INPE-2: Cross-reference glossary term to first use
<http://review.oais.info/show_bug.cgi?id=327> 

The author of this proposal, for transforming it in a Brazilian Standard
(ABNT/BR) had to translate to the Portuguese the previous OAIS document ISO
14721:2012, which contains the document CCSDS 650.0-M-2. The proposal being
made in this current RID h... 

NO CHANGE

328 <http://review.oais.info/show_bug.cgi?id=328>  

OAIS Jun 

Section 

1 

		INPE-3: Check that there are no missing DEFINITION(s) of
ACRONYM(s) or ABBREVIATION(s)  <http://review.oais.info/show_bug.cgi?id=328>

The author of this proposal, for transforming it in a Brazilian Standard
(ABNT/BR) had to translate to the Portuguese the previous OAIS document ISO
14721:2012, which contains the document CCSDS 650.0-M-2. The proposal being
made in this current RID h... 

NO CHANGE

But ask if errors have been identified

329 <http://review.oais.info/show_bug.cgi?id=329>  

OAIS Jun 

Section 

1 

		ESA - Definition of Persistent and Unique Identifiers
<http://review.oais.info/show_bug.cgi?id=329> 

Missing definitions 

Needs discussion

330 <http://review.oais.info/show_bug.cgi?id=330>  

OAIS Jun 

Section 

1 

		ESA-CA-01 Rotate Fig 4-29
<http://review.oais.info/show_bug.cgi?id=330> 

Consistency with other OAIS figures 

NO CHANGE

331 <http://review.oais.info/show_bug.cgi?id=331>  

OAIS Jun 

Section 

1 

		ESA-CA-02 Make references to FAIR
<http://review.oais.info/show_bug.cgi?id=331> 

Beneficial to add reference to FAIR 

NO CHANGE

332 <http://review.oais.info/show_bug.cgi?id=332>  

OAIS Jun 

Section 

1 

		ESA-CA-03 Make reference to DOI
<http://review.oais.info/show_bug.cgi?id=332> 

Reference to DOIs 

CHANGE AGREED

3.	OAIS-IF

a.	Steve may sent out updated diagrams
b.	Updated detailed interface document available at
https://www.dropbox.com/s/56x45hsxy6xxt5y/OAIS-IF%20details20210319.docx?dl=
0 
c.	The last version of the draft GB is
https://www.dropbox.com/s/oze4kbj9z7rn9fk/OAIS-IF%20Rationale%20Scenarios%20
and%20Requirements-20210227.docx?dl=0 .

. 

..David

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20210322/0b12e41c/attachment-0001.htm>