[Moims-dai] Reminder of Skype call today (Tuesday)
kearneysolutions at gmail.com
Tue Jul 20 12:37:30 UTC 2021
Sorry, still on the road and won’t be able to attend. Will be back next week, I think.
Sent from my mobile thing.
> On Jul 20, 2021, at 5:20 AM, david at giaretta.org wrote:
> 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:
> *Don't have Skype yet? Download it before you join https://www.skype.com
> Draft agenda:
> Reminder that we need to update project plan for CWE, in particular the GB and Abstraction Layer
> Report about progress on ISO and Control Authority Blue Book
> OAIS-IF :
> Details from previous 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/xntabui4nssftwe/OAIS-IF%20Rationale%20Scenarios%20and%20Requirements-20210705.docx?dl=0 updated to include the discussion of last week PLUS
> I propose renaming Archive Abstraction Layer (AAL) to OAIS-IF Abstraction Layer (OAL), because this is not restricted to Archives
> After the discussion last week I emailed the following:
> At the end of today’s telecon I had a bit of brain fade and I was not clear in my explanations because I said “Specific” where I meant “Generic” several times, which did confuse people.
> The way I look at is:
> The sequence diagram cannot show everything so I focussed on the exchange of general InformationObjects since pretty well everything we deal with in OAIS are InfoObjects -and we even have defined PackagedInformation Objects to encapsulate the Information Packages as InformationObjects in Steve’s class diagrams.
> An InformationObject is a DataObject plus RepInfo, so the task is to make sure that, if at all possible, enough RepInfo is provided. That is what the sequence diagram aims at showing.
> It purposely does not show anything about search or about selecting which InfoObject to ask for, whether that is science Information, ProvenanceInfo, etc. That is for another diagram, maybe after a bit of prototyping.
> In terms of defining the programming interfaces we COULD do the following. The revised OAIS relates the Provenance etc to the DataObject. Therefore asking for other parts of the OAIS Info Model could be dealt with by basing things on the DataObject, (for example the science DataObject, or the ProvenanceDataObject etc etc etc). So we could ask for DataObjectID.ProvenanceDataObjectID, from which one can get the RepInfo for the ProvenanceInfo.
> The Generic adapter is an attempt to put everything which is common into one place so we do not have lots of duplication of code (of course someone may want to write their own version, implementing the BB). It deals with the negotiations/iterations about RepInfo – of course it has to refer back to the User to see if more RepInfo is needed, or to the archive to see if it has more RepInfo etc. So it just deals with identifiers essentially. It does not understand the OAIS IM, it just passes the requests through.
> The Specific adapters –are specific to either end of the communication e.g the consumer and the archive.
> The archive specific adapter has to know about the Info Model in that it needs to know (perhaps using a database or config file)
> How to get the DataObject
> how to get RepInfo for that DataObject (actually it gets the DataObject which encodes the RepInfo e.g a serialised Java class, or an EAST description etc,etc)
> how to get the Provenance for that DataObject (actually it gets the DataObject which encodes the Provenance e.g a PREMIS file or a list of events or a text file which describes what has happened)
> etc for the other parts of the OAIS IM.
> The Consumer specific adapter needs to know about the OAIS-IM in that it needs to know how/whether the existing software can deal with Provenance etc etc
> Hope that helps.
> MOIMS-DAI mailing list
> MOIMS-DAI at mailman.ccsds.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MOIMS-DAI