[Moims-dai] Reminder of Skype call tomorrow (Tuesday)

[david at giaretta.org]

Meeting: 10:00 Tuesday (Washington DC time), 1500 UK time, 1600 Paris time.

 

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.	Reminder that we need to update project plan for CWE, in particular
the GB and Abstraction Layer
2.	OAIS-IF 

a.	Mario reminded us that SM&C WG and in particular the MAL that has
identified a set of generic Interaction Patterns. See
https://github.com/esa/mo-services-java 
b.	Details from last week: 

                                                               i.
Interactions - from Steve -
https://www.dropbox.com/s/dnftuks5nvixdl0/Interactions_210608.jpg?dl=0

                                                             ii.      WHITE
BOOK FROM Steve -
https://www.dropbox.com/s/fdd8ec5cq2y574z/02_White_Book_Recommended_Standard
_OAIS-IF_Draft_191216%20v5.3%2006_ComparedCombined_04_05_210524.docx?dl=0

                                                           iii.
Component diagram from Steve -
https://www.dropbox.com/s/5fsdmfcchzcqpz5/Component_Diagram_210601.jpg?dl=0

                                                           iv.      Steve
may sent out updated document/diagram

                                                             v.      The
last version of the draft GB is
https://www.dropbox.com/s/k7s1s7xh9tt01wt/OAIS-IF%20Rationale%20Scenarios%20
and%20Requirements-20210516.docx?dl=0 - this includes my thoughts on
sequence diagrams, messages, etc.

                                                           vi.      DG's
sequence diagram at
https://www.dropbox.com/s/1t1cma4anf49cm4/SequenceDiagram-with-adapters-v2.j
pg?dl=0 with, as requested last week, explanation of the numbered arrows as
follows

1)      Each will need to buy/borrow/create their specific portion of the
adapter that depends upon its specific software design and capabilities e.g.


a.       for an InfoSource - is it a simple file server which we can
supplement with a database of RepInfo etc         [1]

b.       for an InfoRequester - can it deal with tables and/or images or is
it only for displaying documents etc               [2]

2)      They each then install the generic portion of the adapter - I think
this can be common to all.                                       [3], [4]

This generic portion does the following things:

a.       Find out about InfoSource using interface we define

b.       Register itself and the InfoSource with the Switchboard e.g. how
others can communicate with it - HTTP/port80 or HTTP/port 2678 or REST or
CORBA or RMI etc etc

This is done just once for each source (or requester)
[5], [6]

3)      During operations the requester discovers somehow that it needs some
information from an InfoSource - how this is done is not covered here. I
think lots of work has been done by others, and OAIS does not really provide
any guidance.

4)      InfoRequester generic adapter finds out from the Switchboard how to
talk to the InfoSource in order to fit into the "OAIS-IF world", and sets up
the communication [7].[8], [9]

5)      The specific adapter of InfoRequester passes on the request to the
generic adapter which passes on the request to the InformationSource generic
adapter         [10], [11]

6)      The generic adapter of the InfoSource receives the request and
passes it to the specific adapter which gets the DataObject and RepInfo (at
least the start of the RepInfoNetwork) and passes that back
[NOT SHOWN]

7)      The InfoSource generic adapter creates an PackagedInfo object and
sends that to the generic adapter of the InfoRequester  [12]

8)      The generic adapter of the InfoRequester asks the specific adapter
if this is OK. If not then the generic adapter exchanges messages with the
InfoSource generic adapter, which may need to talk to the InfoSource
specific adapter.
[13], [14], [15], [16], [17]

9)      PackagedInformation packages are send containing RepInfo until the
InfoRequester is satisfied, or else a strategy is decided to use
Transformation, if the InfoSource can do that
[18], [19], [20], [21]

10)   It may be that a Registry of RepInfo (essentially another
InformationSource) is available and known to the generic adapter, and
additional RepInfo may be obtained from that.
[22], [23]

 

Regards

 

..David

 

 

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