[Moims-dai] Notes from this week's meet and agenda for Washington

[david at giaretta.org]

The draft agenda for the Washington meeting is available at
https://cwe.ccsds.org/moims/docs/MOIMS-DAI/Meeting%20Materials%20and%20Minut
es/2024-04-Washington-DC/CCSDS%20MOIMS-DAI%20Spring%202024%20Agenda.docx?d=w
40928681dced4a5a84312c7224bc1757

 

Please let me know what alterations are needed.

 

I apologise that I will not be able to attend in person because we are
moving house and there are a lot of things to be done, however I should be
able to join the meetings virtually all day - I have the morning to do
moving stuff because of the time difference in the UK!

 

This week we discussed some of the remaining RIDS

 

*	http://review.oais.info/show_bug.cgi?id=387    - agree that this is
an OK summary of changes

http://review.oais.info/show_bug.cgi?id=388 -   agree that this is an OK
summary of changes

*	http://review.oais.info/show_bug.cgi?id=349 - need input from JGG
*	an old one we need to resolve
http://review.oais.info/show_bug.cgi?id=389  - some duplication must be
sorted out and gives us an opportunity to add an important missing metric. 

*	We will close this next week. Please provide any inputs.

Other points:

*	ESA draft OAIS-IF YB should available next week
*	ESA feedback on OAIS-IF BB depends on availability of Massimo, the
ESA developer, but should be soon.

 

I have proposed a JSON schema for the Information Packages, which seems to
validate against the example IPs and AIP in the BB. This allows the BB to be
more precise, but no changes needed in existing software which were based on
those examples.

 

One extra thing that was added, but not shown in those examples is the
encoding of embedded binary objects. This makes the JSON able to point to an
external file, or to an internal part of the JSON (using JSONPath) or embed
a binary object in the JSON - just as XFDU allows. The tricky point is that
JSON must be  text (actually UTF-8) for interchanges between different
systems (https://www.rfc-editor.org/rfc/pdfrfc/rfc8259.txt.pdf), so binary
files must be encoded appropriately. The actual encoding should be part of
the RepInfo.

 

Terry raised the point that binary files that were not 8-bit multiples could
be a problem. My assumption is that padding would solve this, with
appropriate RepInfo, but others should think about it.

 

..Regards

 

..David

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20240411/678655f5/attachment.htm>