[Moims-dai] Draft interoperability layered model

David Giaretta david at giaretta.org
Wed Jul 13 08:32:14 UTC 2016

Hi Mike


Yes, let's move on using chart 2. I'll provide comments/ideas for this

You are right, the yellow bar is about support processes which are needed
for preservation - I was not sure how best to indicate these. The idea was
that the AIP itself may/will evolve over time e.g. adding Representation
Information etc as the Designated Community, technology etc changes. Maybe
the AIP bar along the bottom could show several segments - but perhaps that
activity should show in a different type of diagram. 




From: Moims-dai [mailto:moims-dai-bounces at mailman.ccsds.org] On Behalf Of
Mike Kearney
Sent: 12 July 2016 22:37
To: 'MOIMS-Data Archive Ingestion' <moims-dai at mailman.ccsds.org>
Subject: Re: [Moims-dai] Draft interoperability layered model


Since we didn't have much time to discuss this in our telecon this morning,
I thought I'd try to work some of this across email with another chart
revision.  David, look at this and see if it retains your concepts.  Your
original chart is chart 1, my new chart is chart 2.  


What I added was.


The little curly-cue interface symbols got quite hard to comprehend, so I
replaced them with simple lines from the bindings.  This required text to
identify the end-points of discipline-specific services in the
representation info and the data.   


I added where I thought the communications services were, effectively
delineating the boundary between user (producer/consumer) systems and
archive systems.  


I also added "Archive Common Calls" for generic functions that are not
discipline specific.  And noted expandability by adding "Other TBD


Behind the Backup chart is a slightly earlier version that doesn't delineate
discipline-specific "ports" in the archive system.  Simpler, but less


David, I'm not sure of the significance of the yellow "Preservation
Activities" layer at the very bottom.  Looks like we're mixing systems and
processes together with that.  Can you clarify?  


Shall we move on to work from Chart 2 from this point forward?  




   -=- Mike


Mike Kearney

Huntsville, Alabama, USA


From: Mike Kearney [mailto:kearneysolutions at gmail.com] 
Sent: Tuesday, July 12, 2016 7:07 AM
To: 'MOIMS-Data Archive Ingestion' <moims-dai at mailman.ccsds.org
<mailto:moims-dai at mailman.ccsds.org> >
Subject: RE: [Moims-dai] Draft interoperability layered model


Good topics for discussion in our telecon this morning.  I'm confused by
several aspects of this version, but I'm sure you can set me straight.  


Unfortunately I have a doctor appointment an hour after telecon start, so
I'll only be able to attend for the first half-hour.  


   -=- Mike


Mike Kearney

Huntsville, Alabama, USA


From: Moims-dai [mailto:moims-dai-bounces at mailman.ccsds.org] On Behalf Of
David Giaretta
Sent: Tuesday, July 12, 2016 4:43 AM
To: 'MOIMS DAI List' <moims-dai at mailman.ccsds.org
<mailto:moims-dai at mailman.ccsds.org> >
Subject: [Moims-dai] Draft interoperability layered model


Here is a revised model. The diagram tries to bring in Annex E and shows
Representation Information needed for the data and the PDI (and also the

The AIP, supported by the Preservation activities, provide the transmission
mechanism from one archive to another and/or from one time to another.





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20160713/38fcf1d5/attachment.html>

More information about the MOIMS-DAI mailing list