[Moims-dai] Use of SYSML was RE: [EXTERNAL] Reminder of Skype call Tuesday
Hughes, John S (US 398B)
john.s.hughes at jpl.nasa.gov
Mon Mar 29 13:18:45 UTC 2021
* I was really only asking which one Steve had used. I thought I remembered him saying early in the development that he used both, but wasn't sure.
Correct, the lab has a institutional license for Magic Draw, now Cameo System Modeler. The SysML plugin was included several years ago and it is not always obvious when one has crossed over. I was going to wait on Peter's input for the CCSDS perspective of SysML's usefulness. Of course all opinions are welcome and I will look into the extend to which I have taken advantage of it.
Thanks,
Steve
From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org> On Behalf Of kearneysolutions at gmail.com
Sent: Sunday, March 28, 2021 2:32 PM
To: 'MOIMS-Data Archive Interoperability' <moims-dai at mailman.ccsds.org>
Subject: Re: [Moims-dai] Use of SYSML was RE: [EXTERNAL] Reminder of Skype call Tuesday
Hey, David,
* You made a comment "Should this be SysML? Or both UML and SysML? "
I was really only asking which one Steve had used. I thought I remembered him saying early in the development that he used both, but wasn't sure. I wasn't advocating SysML, just trying to ensure the statement was historically correct.
The main point of the paragraph was "should not be used without close scrutiny". It's the standard CCSDS caveat that any prototype in support of the standard does not carry the weight of the standard, and should be used very carefully. If you would like to reword it so as not to "conflate" things, by all means proceed.
I concede on all other points. You're certainly the greater expert in that domain.
-=- 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 david at giaretta.org<mailto:david at giaretta.org>
Sent: Friday, March 26, 2021 8:17 AM
To: 'MOIMS-Data Archive Interoperability' <moims-dai at mailman.ccsds.org<mailto:moims-dai at mailman.ccsds.org>>
Subject: Re: [Moims-dai] Use of SYSML was RE: [EXTERNAL] Reminder of Skype call Tuesday
I forgot to suggest that if we follow MAL then the package structure could be something like those below. My assumption is that we want the "top level" to be generic, then we want separate packages as we include more specific models e.g. for RepInfo or Provenance or archive access. In my draft I put everything at the top level for convenience, but separating things into sub-packages gives more flexibility.
1. the OAIS-IF package: org.ccsds.moims.dai.oaisif; :
* interface definitions: org.ccsds.moims.dai.oaisif.interfaces;
i. RepresentationInformation detailed interfaces: org.ccsds.moims.dai.oaisif.interfaces.repinfo;
ii. Provenance detailed interfaces: org.ccsds.moims.dai.oaisif.interfaces.provenance;
iii. Negotiation interfaces detailed interfaces: org.ccsds.moims.dai.oaisif.interfaces.negotiation;
iv. Local archive adapter detailed interfaces: org.ccsds.moims.dai.oaisif.interfaces.local;
v. Interfaces to be used by consumer applications: org.ccsds.moims.dai.oaisif.interfaces.consumer;
* Interfaces to be used by consumer applications for table access: org.ccsds.moims.dai.oaisif.interfaces.consumer.tables;
* Interfaces to be used by consumer applications for image access: org.ccsds.moims.dai.oaisif.interfaces.consumer.image;
* etc
* Reference Implementation: org.ccsds.moims.dai.oaisif.impl;
i. Reference Implementation for RepInfo: org.ccsds.moims.dai.oaisif.impl.repinfo;
ii. Reference Implementation for Provenance: org.ccsds.moims.dai.oaisif.impl.provenance;
iii. Reference Implementation for negotiation: org.ccsds.moims.dai.oaisif.impl.negotiation;
iv. Reference Implementation for reasonably generic fileserver archive local access: org.ccsds.moims.dai.oaisif.impl.local.fileserver
..David
From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org<mailto:moims-dai-bounces at mailman.ccsds.org>> On Behalf Of david at giaretta.org<mailto:david at giaretta.org>
Sent: 26 March 2021 11:58
To: 'MOIMS-Data Archive Interoperability' <moims-dai at mailman.ccsds.org<mailto:moims-dai at mailman.ccsds.org>>
Subject: [Moims-dai] Use of SYSML was RE: [EXTERNAL] Reminder of Skype call Tuesday
HI Mike
You made a comment "Should this be SysML? Or both UML and SysML? "
My view is that I cannot see the reason for doing this in SYSML when we already have the UML, unless there is some aspect of the system which only SYSML enables us to design. Otherwise it is just unproductive.
The second paragraph you propose adding:
Users are cautioned that this is a prototype implementation of a model that was used for development of the OAIS-IF standards, and they should not be used without close scrutiny by the user organizations's software development and systems engineering staff to insure that they are suitable for their intended use. CCSDS is not responsible for any negative outcome that results from the user's application of the OAIS-IF UML Model(s). In particular, usage of those models in no way guarantees conformance to OAIS-IF (see section 1.5.) More information is available at the above link on the SANA registry.
This seems to be conflating the design model (UML encoded in XMI ?) with the implementation. In terms of implementation I imagine we would have, for example in Java,
(1) code for the interfaces, that can be generated automatically by design tools, plus
(2) code which implements those interfaces for some specific case, although some code may be fairly general such as for the "negotiate" class.
I note that for Java, and maybe some other programming languages, we will need to define a package structure for the interfaces. In my drafts I used "info.oais." because I own the domain oais.info. However perhaps there is some CCSDS standard way of doing this. For example https://public.ccsds.org/Pubs/523x1m1.pdf<https://urldefense.us/v3/__https:/public.ccsds.org/Pubs/523x1m1.pdf__;!!PvBDto6Hs4WbVuu7!edhLfppNaf-m32GdolLgzEkMW0RhP1m0bCOc9RAeiTO1L4UEJTAjncmNb0xyYaPz0tshFFA$> says:
3.1.4The packages provided by the API shall be:
a)the MAL package: org.ccsds.moims.mo.mal;
b)the data structures package: org.ccsds.moims.mo.mal.structures;
c)the consumer package: org.ccsds.moims.mo.mal.consumer;
d)the provider package: org.ccsds.moims.mo.mal.provider;
e)the broker package: org.ccsds.moims.mo.mal.broker.
3.1.5The MAL package name shall be added to the SANA registry JavaBindingNamespace and shall refer to the MAL Java API document 'CCSDS 523.1-M-1'.
Cheers
..David
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: 24 March 2021 01:49
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] [EXTERNAL] Reminder of Skype call Tuesday
As discussed today, attached is my contribution concerning planned availability of UML models. Section 1.6.
Steve, I shortened the file name a little bit because sometimes things get flakey with a filename that's too long. Hope this works.
-=- 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: Tuesday, March 23, 2021 6:55 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] [EXTERNAL] Reminder of Skype call Tuesday
Hi all,
As requested, attached is the document before changes were accepted.
Thanks,
Steve
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: Tuesday, March 23, 2021 8:53 AM
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] [EXTERNAL] Reminder of Skype call Tuesday
Hi all,
Attached is a copy of the OAIS IF BB with several options inserted for discussion.
Thanks,
Steve
From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org<mailto:moims-dai-bounces at mailman.ccsds.org>> On Behalf Of david at giaretta.org<mailto:david at giaretta.org>
Sent: Monday, March 22, 2021 2:42 PM
To: MOIMS-DAI List <moims-dai at mailman.ccsds.org<mailto:moims-dai at mailman.ccsds.org>>
Subject: [EXTERNAL] [Moims-dai] Reminder of Skype call Tuesday
Meeting: 10:00 Tuesday (Washington DC time), but because of Daylight Saving Time changes the time for the meeting in Europe will be 1400 UK time, 1500 Paris time this week and next week. After that Europe also moves to Daylight Saving Time and we return to the normal schedule.
If you do not receive a notification from Skype then please join it by clicking the link:
https://join.skype.com/ykyu5SIPhSnD<https://urldefense.us/v3/__https:/join.skype.com/ykyu5SIPhSnD__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLluTNtYk$>
*Don't have Skype yet? Download it before you join https://www.skype.com<https://urldefense.us/v3/__https:/www.skype.com__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLxkgiIxc$>
Draft agenda:
1. Feedback from MOIMS AD on books - I received the following rapid response from Marc Duhaze. COMMENTS ADDED (please check, especially the text proposed)
Hi All,
First of all, I'm a newbie in this domain, so please be tolerant ;)
About CCSDS 652.1-M-2-updated : (see https://www.dropbox.com/s/80xzgt3qpql633k/652x1m2_20210116.doc?dl=0<https://urldefense.us/v3/__https:/www.dropbox.com/s/80xzgt3qpql633k/652x1m2_20210116.doc?dl=0__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoL_HHEd_w$>)
* As it is mainly a clone of the ISO/IEC 17021-1 standard fitted in a CCSDS template,
* I have no specific comment, so it's fine for me
READY TO SEND TO AD
About CCSDS 653.0-R-1 : (see https://www.dropbox.com/s/r2tmotj8ejw5lm0/CCSDS653.0R1-20210322.docx?dl=0<https://urldefense.us/v3/__https:/www.dropbox.com/s/r2tmotj8ejw5lm0/CCSDS653.0R1-20210322.docx?dl=0__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLzv1J72Q$>)
* Initial page : reference should be CCSDS 653.0-R-1, no ?
DONE, also changed date to March 2021, but expect CCSDS Editor will make appropriate changes
* About Brigitte comment : p3-1
* "I would have expected a more "in depth" analysis of the project documentation that should be preserved at each phase."
* David answer : "Yes, specific aspects of the project documentation will almost certainly be preserved"
* I'm not sure about what was expected by Brigitte and so if David answers the question, however my opinion is that a lot of examples of possible project documents are given for each "step" of the collection group. So I assume that at the end of a phase, all the document produced during the different steps of a collection group are preserved. So to answer the Brigitte question, you should perhaps add a sentence in that way, at the end of §3.2
Sentence added at section 3.2 "Important types of information are identified in section 4 and a number of checklists are provided in ANNEX C and ANNEX D, but the variety of potential projects and their documents means that only general guidelines can be given."
* About Mario comment : p4-4
* "All information in the PDI are already described in the OAIS book at high level. In my understanding, the value of this book should be in going one level down and prescribe, for each PDI, the minimum common denominator of required information..."
* David answer : "The point is that PDI, and in particular Provenance, is to be collected throughout, rather than left to the end. In OAIS this is implicit. This document makes it explicit."
* I'm not sure the answer covers the question raised by Mario. Is it possible to split the information list provided for each type (Reference, Provenance, Context, ...) into different categories such as "required information", "recommended information", "optional information" ... ?
Add paragraph to 4.1.2
Of these the Provenance is likely to be required over the entire life of the project, and beyond, being relevant to all subsequent outcomes of the project, and so is always required. Reference, Fixity, Context and Access Rights Information may not be required through all successive stages, unless relevant to the Provenance.
TO BE DISCUSSED
* I agree with other answers to Mario and Brigitte comments and have no other comment
OK
About CCSDS 652.0-W(M)-1.1 : (see https://www.dropbox.com/s/q8uofeoewdllrrw/652x0w1x1-20210322.doc?dl=0<https://urldefense.us/v3/__https:/www.dropbox.com/s/q8uofeoewdllrrw/652x0w1x1-20210322.doc?dl=0__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoL-sjt_tM$>)
* Page 1-5 : you missed a "written" : "Preservation Strategic Plan: A written statement..." to change to "...documented statement"
DONE
* About Mario comment : p3-5
* "This seems to me a characteristic of any good work position. I would remove it from here. By the same token, you could also ask for full medical coverage for the repository staff, ..."
* David answer "We disagree. Our experience is that it is worth statin this metric explicitly. If one goes down the route you propose we could remove most metrics"
* Sorry Mario ;) , but I agree with David answer. @Mario, what about you ?
OK
* About Brigitte comments p5-1 and 5-11
· "BBh34: besides adapting and changing its hardware and software, it seems to me that the repository architecture should be designed so that it can cope with these changes with a minimum of service perturbation (for instance having dedicated test environment to validate new software release and to train staff, provide possibilities of roll-back when installing new version, privilege whenever possible backward compatibility).
If the repository architecture is not correctly dimensioned, any intervention will lead to more or less important service interruptions.
Consider adding a requirement/metric dedicated to this issue (the architecture must be designed and dimensioned to meet the preservation objectives)."
· David answer " It was felt that, while what you write is correct, it seemed unnecessary to demand that auditors review the overall design of the archive, but the system requirement/design documents may be presented as evidence"
* BBh39: cf. BBh34. Prior to that, the repository architecture should be adequately dimensioned
* David answer :" Metrics covering adequate scaling already in the document"
* To me, the points raised by Brigitte are covered by exiting requirements in the document such as
* "The repository shall identify and manage the risks to its preservation operations and goals associated with system infrastructure."
* "The repository shall have adequate hardware and software support for backup functionality sufficient for maintaining the system support to preserve the repository content and tracking repository functions. "
* I agree with other answers to Mario and Brigitte comments and have no other comment
OK
Regards.
Marc.
1. OAIS - please add comments to OPEN OAIS RIDS, especially about DOI and FAIR. It would be good to close these to the point of asking for being able to ask for the agreement of the submitter.
Suggested Disposition
312<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=312__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoL8CfU-rI$>
OAIS Jun
Section
A
Consider updating text about existing archives.
NO CHANGE
Do not put anything in
322<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=322__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLFY0hxp0$>
OAIS Jun
Section
2
Clarify usefulness of OAIS for Interoperability, re-reproducibility and re-use <https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=322__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLFY0hxp0$>
The requirements for preservation are also important for current use of information. This change will make that point clearer.
CHANGE PROPOSED
325<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=325__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLZptb0lQ$>
OAIS Jun
Section:
9
NASA/JSC 1 Only one set of access rights per data object <https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=325__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLZptb0lQ$>
Access control enforcement will be greatly simplified.
CHANGE PROPOSED
326<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=326__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLFi3pbPM$>
OAIS Jun
Section:
2
INPE-1:Detailed review be made of Figure A-1 in page A-2 in order that it may guaranteed that the functionally that it represents -fully- corresponds to the naturally more detailed functionality that is represented in the set of Figures 4-2 through 4-7. <https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=326__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLFi3pbPM$>
he author of this proposal, for transforming it in a Brazilian Standard (ABNT/BR) had to translate to the Portuguese the previous OAIS document ISO 14721:2012, which contains the document CCSDS 650.0-M-2. The proposal being made in this current RID ha...
NO CHANGE
Response has been proposed
327<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=327__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLhg7m4yI$>
OAIS Jun
Section
1
INPE-2: Cross-reference glossary term to first use <https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=327__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLhg7m4yI$>
The author of this proposal, for transforming it in a Brazilian Standard (ABNT/BR) had to translate to the Portuguese the previous OAIS document ISO 14721:2012, which contains the document CCSDS 650.0-M-2. The proposal being made in this current RID h...
NO CHANGE
328<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=328__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLqa9ZwHc$>
OAIS Jun
Section
1
INPE-3: Check that there are no missing DEFINITION(s) of ACRONYM(s) or ABBREVIATION(s) <https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=328__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLqa9ZwHc$>
The author of this proposal, for transforming it in a Brazilian Standard (ABNT/BR) had to translate to the Portuguese the previous OAIS document ISO 14721:2012, which contains the document CCSDS 650.0-M-2. The proposal being made in this current RID h...
NO CHANGE
But ask if errors have been identified
329<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=329__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLU619AnM$>
OAIS Jun
Section
1
ESA - Definition of Persistent and Unique Identifiers <https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=329__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLU619AnM$>
Missing definitions
Needs discussion
330<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=330__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoL0I1-J9I$>
OAIS Jun
Section
1
ESA-CA-01 Rotate Fig 4-29 <https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=330__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoL0I1-J9I$>
Consistency with other OAIS figures
NO CHANGE
331<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=331__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLnl5RqA0$>
OAIS Jun
Section
1
ESA-CA-02 Make references to FAIR <https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=331__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLnl5RqA0$>
Beneficial to add reference to FAIR
NO CHANGE
332<https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=332__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoL8XIbduE$>
OAIS Jun
Section
1
ESA-CA-03 Make reference to DOI <https://urldefense.us/v3/__http:/review.oais.info/show_bug.cgi?id=332__;!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoL8XIbduE$>
Reference to DOIs
CHANGE AGREED
1. OAIS-IF
* Steve may sent out updated diagrams
* Updated detailed interface document available at https://www.dropbox.com/s/56x45hsxy6xxt5y/OAIS-IF%20details20210319.docx?dl=0<https://urldefense.us/v3/__https:/www.dropbox.com/s/56x45hsxy6xxt5y/OAIS-IF*20details20210319.docx?dl=0__;JQ!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoL2qW6Snw$>
* The last version of the draft GB is https://www.dropbox.com/s/oze4kbj9z7rn9fk/OAIS-IF%20Rationale%20Scenarios%20and%20Requirements-20210227.docx?dl=0<https://urldefense.us/v3/__https:/www.dropbox.com/s/oze4kbj9z7rn9fk/OAIS-IF*20Rationale*20Scenarios*20and*20Requirements-20210227.docx?dl=0__;JSUlJQ!!PvBDto6Hs4WbVuu7!ZrV2CexL9YX24H0xAKavLeODxg1qYomyknZ5jJjZgnWj0jcYWjblLFakbNqgkEoLAFSVm1k$> .
.
..David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20210329/9bac9df9/attachment-0001.htm>
More information about the MOIMS-DAI
mailing list