[Moims-dai] Component Diagram and Updated Book

Fri Oct 9 13:24:59 UTC 2020

I think I was responsible for the "implementation framework" bloopers, so I
fixed them in the attached and the version in the dropbox.  

David, on #2, I expect not only OAIS-IF external interfaces (with client and
archive) to be normative, but also OAIS-IF internal interfaces (between
consumer I/F and Archive Abstraction Layer (AAL), between producer I/F and
AAL, and between AAL and bindings).  As we have anticipated developing blue
books for those interfaces spawned from the ADD.  Including PAIS, PAIP,
CAIS, CAIP as we described in the PPT that we sent to the CMC in 2017.

Not sure what to say about #1.  Normally section 2 is non-normative.  Maybe
the functional model needs to be moved to section 3 if we want it normative?
Actually that whole discussion anticipates future comments from Peter.
Maybe in terms of what goes in what (non-)normative sections, we should ask
Peter before we get too far down the road.  

   -=- Mike

Mike Kearney

Huntsville, Alabama, USA 

From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org> On Behalf Of
david at giaretta.org
Sent: Friday, October 9, 2020 6:37 AM
To: 'Hughes, John S (US 398B)' <john.s.hughes at jpl.nasa.gov>
Cc: 'MOIMS-Data Archive Interoperability' <moims-dai at mailman.ccsds.org>
Subject: Re: [Moims-dai] Component Diagram and Updated Book

Hi Steve

A few points from me that will probably not come as a surprise:

1.	Mike's additions puts the things about the Functional Model i.e. all
section 2 - in context i.e. non-normative. 
2.	Mike says "specified normative functions of the interoperable
interfaces" - which I suppose are the external interfaces I expect.
3.	I would have expected a lot more in terms of Representation
Information
4.	I would have expected some APIs - I guess these come in the
following versions.

Regards

..David

From: david at giaretta.org <mailto:david at giaretta.org>  <david at giaretta.org
<mailto:david at giaretta.org> > 
Sent: 08 October 2020 17:50
To: 'Longstreth at acm.org' <Longstreth at acm.org <mailto:Longstreth at acm.org> >;
'MOIMS-Data Archive Interoperability' <moims-dai at mailman.ccsds.org
<mailto:moims-dai at mailman.ccsds.org> >; 'Hughes, John S (US 398B)'
<john.s.hughes at jpl.nasa.gov <mailto:john.s.hughes at jpl.nasa.gov> >;
'kearneysolutions at gmail.com' <kearneysolutions at gmail.com
<mailto:kearneysolutions at gmail.com> >
Subject: RE: [Moims-dai] Component Diagram and Updated Book

You use "Implementation Framework" instead of "Interoperability Framework"
in a couple of places.

..David

From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org
<mailto:moims-dai-bounces at mailman.ccsds.org> > On Behalf Of Terry Longstreth
Sent: 08 October 2020 17:06
To: 'Hughes, John S (US 398B)' <john.s.hughes at jpl.nasa.gov
<mailto:john.s.hughes at jpl.nasa.gov> >; kearneysolutions at gmail.com
<mailto:kearneysolutions at gmail.com> ; MOIMS-Data Archive Interoperability
<moims-dai at mailman.ccsds.org <mailto:moims-dai at mailman.ccsds.org> >
Subject: Re: [Moims-dai] Component Diagram and Updated Book

Steve,

I don't have Microsoft and I'm not sure if Libreoffice interprets the
non-standard markup correctly so I didn't want to redline your  document (or
Mike's version). 

Some things I noticed: 

1.	Section 2.3 Derived Interfaces, lists two package types for
consumers, only one of which is a DIP. This will always be controversial,
and in discussions (last month?) we suggested the diagrams use "IP" instead
of DIP to accommodate all packages delivered to consumers.  This dichotomy
should also be mentioned in Section 2.1 to reflect the distinction between
true archived materials (i.e. derived directly from AIPs) and ancillary data
such as search request responses, scheduling dialogs, or Report Assistance
delivered to the Consumer. Of course you could leave such dialog or
ancillary interactions outside of the OAISIF altogether, and leave those
things to implementers to solve on their own. I'm not sure they'd
necessarily impact the preservation life cycle.
2.	(I know this is a real nit) But book dates, in the footer and on the
title page don't match.  
3.	Figure 3 Caption (sound it out)

On 2020-10-07 10:11 PM, kearneysolutions at gmail.com
<mailto:kearneysolutions at gmail.com>  wrote:

Steve, attached are my draft additions to explain the boundaries of
normative material in the architecture, as we discussed during the telecon
on Tuesday.  I turned track changes on, and you'll find updates only in
sections 1.1 and 1.5.  

All, if you're submitting comments/redlines to Steve, remember to turn on
Track Changes first. they're off by default in the copy that Steve sent.  

   -=- Mike

Mike Kearney

Huntsville, Alabama, USA 

From: MOIMS-DAI  <mailto:moims-dai-bounces at mailman.ccsds.org>
<moims-dai-bounces at mailman.ccsds.org> On Behalf Of Hughes, John S (US 398B)
via MOIMS-DAI
Sent: Tuesday, October 6, 2020 10:11 AM
To: MOIMS-Data Archive Interoperability
<mailto:moims-dai at mailman.ccsds.org> <moims-dai at mailman.ccsds.org>
Cc: Hughes, John S (US 398B)  <mailto:john.s.hughes at jpl.nasa.gov>
<john.s.hughes at jpl.nasa.gov>
Subject: Re: [Moims-dai] Component Diagram and Updated Book

Hi all,

Attached please find the latest version of the book in both .doc and .pdf
formats.

Thank you,

Steve

From: Hughes, John S (US 398B) <john.s.hughes at jpl.nasa.gov
<mailto:john.s.hughes at jpl.nasa.gov> > 
Sent: Monday, October 5, 2020 1:45 PM
To: MOIMS-Data Archive Interoperability <moims-dai at mailman.ccsds.org
<mailto:moims-dai at mailman.ccsds.org> >
Cc: Hughes, John S (US 398B) <john.s.hughes at jpl.nasa.gov
<mailto:john.s.hughes at jpl.nasa.gov> >
Subject: FW: Component Diagram and Updated Book

Hi all,

David mentioned that he will not be able to attend tomorrow's meeting of the
MOIMS Data Archive Interoperability group and asked that we continue
discussion of the OAIS-IF. 

In preparation, attached are the latest Component diagrams and an updated
version of the book. To help focus the discussion I like to review the set
of elements to determine whether we have the minimal set needed. 

Thanks,

Steve

_______________________________________________
MOIMS-DAI mailing list
MOIMS-DAI at mailman.ccsds.org <mailto:MOIMS-DAI at mailman.ccsds.org> 
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai

-- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20201009/042d71a9/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 11118 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20201009/042d71a9/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 02_White_Book_Recommended_Standard_OAIS-IF_Draft_191216 v5.3 NewSection3_200927 - MWK Comments 20201009.doc
Type: application/msword
Size: 550400 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20201009/042d71a9/attachment-0001.doc>