[Moims-dai] FW: [EXTERNAL] Interaction pattern discussion
david at giaretta.org
david at giaretta.org
Tue Jun 15 11:37:43 UTC 2021
For completeness here is a copy of the email I sent to Mike commenting on
Nice detailed diagrams - we certainly need this level of detail.
What I meant about adapters was that, as I wrote in the GB, the adapter
surely must depends strongly on the software it is connected to, and is
independent on what is at the other end of the network. Hence the Consumer
(not necessarily Designated Community of the archive being communicated
with) needs to obtain an adapter for its specific s/w. In the GB I gave an
example of a pretty generic adapter for a type of archive. The OAIS-IF may
talk to a registry which keeps copies of adapters for specific client
software, but we would need to discuss that). So the OAIS-IF may know about
some pre-prepared or generic adapters, but it would not be reasonable for
the archive to have a whole set of adapters for everyone.
Also the basic communication between archive and consumer (to use specific
names for the two ends of the communication) will need some "out of band"
communication i.e. not specified by the standard OR we say that it is, for
example specified in the standard as a specific REST request i.e. we say
that one needs HTTP on Port 80 to set up the communications.
My only other point is that there needs to be some iteration about RepInfo
until either the consumer has enough - which may pull RepInfo from other
registries of RepInfo - or else one gives up i.e. someone needs to
"Research/Develop more RepInfo for data set X", as you show in the diagram,
but that must be for the Consumer side - you show it for the Provider.
I hope that helps.
However, I I mentioned, things will be clearer if/when we start
implementations, as long as we recognise what our implicit assumptions are.
From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org> On Behalf Of Hughes,
John S (US 398B) via MOIMS-DAI
Sent: 15 June 2021 12:27
To: MOIMS-Data Archive Interoperability <moims-dai at mailman.ccsds.org>
Cc: Hughes, John S (US 398B) <john.s.hughes at jpl.nasa.gov>
Subject: [Moims-dai] FW: [EXTERNAL] Interaction pattern discussion
Attached please find some Interaction charts draw by Mike as part of an
offline discussion. We can discuss these today.
From: kearneysolutions at gmail.com <mailto:kearneysolutions at gmail.com>
<kearneysolutions at gmail.com <mailto:kearneysolutions at gmail.com> >
Sent: Tuesday, June 8, 2021 12:14 PM
To: david at giaretta.org <mailto:david at giaretta.org> ; Hughes, John S (US
398B) <john.s.hughes at jpl.nasa.gov <mailto:john.s.hughes at jpl.nasa.gov> >;
John Garrett <garrett at his.com <mailto:garrett at his.com> >
Subject: [EXTERNAL] Interaction pattern discussion
Steve: Here is my non-programmer writeup explaining the interaction
patterns, in layman's language, that I volunteered to send you today. Some
of these were not addressed in your UML tool interaction pattern graphics,
and maybe aren't needed or desired. But they just seem to be the dialog
that we discussed. Note that I started with the example that the adapter
was not provided by the archive, but rather another source in the designated
community. A subset (the trivial example) would be where that source is
actually in the archive.
Also, I separated a discovery phase from a data exchange phase, and even
separated the data exchange phase into two examples. consumer and provider.
You can keep or reject any of this.
After I did this, I realized that I could have left the programmer calls
over the arrows like you had (except I'm not capable of writing them) and
had my "layman's language" explanation of each transaction off to one side
in a "notes" column. I think a lot of the discussion today was people not
understanding the labels on each transaction arrow, and it would be less
ambiguous to add notes off to the side like my (occasionally
tongue-in-cheek) transaction labels.
David, we couldn't really figure out what you meant by the adapters were
between my concept and Steve's concept. So these charts may have the same
problem for you that you briefly mentioned before.
Huntsville, Alabama, USA
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MOIMS-DAI