[Moims-dai] OAIS Interoperability Framework

[david]

Hi SteveWe probably will soon need to look also at other types of UML diagrams such as Component and Sequence to show different aspects of the system.One additional consideration is that OAIS has messages such as queries and requests which are not SIPs, which is why I focussed on IPs. In other words I am advocating that we treat even requests and queries as IPs.Finally, my diagrams are in terms of Interfaces (the programming use of that word) rather than Classes because Interfaces allow multiple inheritance for objects, and emphasise the essential methods required while avoiding implementation issues at this stage although these have to be addressed in due course.RegardsDavidSent from my Samsung Galaxy smartphone.
-------- Original message --------From: "Hughes, John S (US 398B) via MOIMS-DAI" <moims-dai at mailman.ccsds.org> Date: 17/03/2020  03:58  (GMT+00:00) 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] OAIS Interoperability Framework 

Hi all,
 
Attached are the latest set of UML diagrams. The diagram previously distributed has been partitioned into three diagrams to simplify discussion. The “mapping” class diagram in particular is similar to the UML
 interface diagram distributed by David. https://docs.google.com/document/d/14V0wN6nEnG2MaSMmNClRzuDrTxcB0zjv0XNw2pdYDI8/edit?usp=sharing

David’s InformationSender and InformationRequester are very interesting and seem to resolve a couple of issues.  I would also appreciate more discussion on the abstraction layer, plugins, etc.
 
Thanks,
Steve
 
 

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