[Moims-dai] Component Diagram - Consumer and Producer Application Update

[kearneysolutions at gmail.com]

My thought is that all the functions (language, capabilities, underlying
protocols) for any given archive should be "bundled" into a single plug-in
(binding/API/protocol) that a user downloads for access to any given
archive.  

 

I did have a notion that perhaps certain vendors (Adobe for PDF, Autodesk
for Autocad, IIPC for HTML, etc.) could provide plugins that are for certain
common data formats so that the plug-in provider (archive or designated
community) doesn't necessarily have to add common file format sensitivity to
their plugin for their archive.  In that case, maybe multiple plugins would
be needed to access an archive that has unique formats plus those common
formats.  This concept is also in the PPT charts that we've been using since
the beginning.  

 

But other than that, I don't think we want multiple plugins for a single
archive, if possible.  

 

As we discussed, the binding should be able to provide access (Level 0) to a
different designated community's archive than he has without the binding.
But it doesn't necessarily translate/convert to formats (Level 1-5) used by
those external to the archive (public, other designated communities, etc.).


 

I switched the lowest from Level 1 to Level 0 when Steve did, but maybe we
should stick with Level 1 for Access, just in case we find something else
later that is even more primitive than just access.  

 

   -=- Mike

 

Mike Kearney

Huntsville, Alabama, USA 

 

From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org> On Behalf Of
garrett at his.com
Sent: Tuesday, May 12, 2020 1:11 AM
To: 'MOIMS-Data Archive Interoperability' <moims-dai at mailman.ccsds.org>
Subject: Re: [Moims-dai] Component Diagram - Consumer and Producer
Application Update

 

Hi,

 

Are there different types of "bindings" we need different terms for?

 

"Binding" of the abstract functions/information to the implementation
programming language/DB/formats

"Binding" of the abstract  functions/information to the actual
archive/producer/consumer capabilities

"Binding" of the abstract/actual  functions/information to the underlying
communication protocols

 

I think we may need to look at all of these aspects.

 

Maybe we need some 3D views to include all of them.

 

May there be peace in your life,

-JOhn 

 

From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org
<mailto:moims-dai-bounces at mailman.ccsds.org> > On Behalf Of
kearneysolutions at gmail.com <mailto:kearneysolutions at gmail.com> 
Sent: Monday, May 11, 2020 7:20 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: Re: [Moims-dai] Component Diagram - Consumer and Producer
Application Update

 

Looks good, Steve, it's getting there.  Still nothing in the binding,
though.  

 

The "Archive Interface" functions; are those in the archive systems, or in
the user systems.  They sort of look to me like they could be in the user
systems, hence the "Archive interface" would be part of the binding.  

 

   -=- Mike

 

Mike Kearney

Huntsville, Alabama, USA 

 

From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org
<mailto:moims-dai-bounces at mailman.ccsds.org> > On Behalf Of Hughes, John S
(US 398B) via MOIMS-DAI
Sent: Monday, May 11, 2020 6:10 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: [Moims-dai] Component Diagram - Consumer and Producer Application
Update

 

Hi all,

 

Attached is the latest version of a Component diagram that maps to Mike's
diagram. The key changes include adding Consumer and Producer applications
to the application layer.

 

Thanks,

Steve

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20200512/f0782244/attachment.htm>