Kaitai Struct uses a specific JSON schema for test output.
I want to target it directly from my target language (Nim) but it is not documented anywhere.

After some experimenting I found out the following keys are supported:

• status
• elapsed
• is_kst

Questions:

1. Are there other keys supported?
2. What exactly does the key elapsed mean?
3. What are all the possible values for th

It's invalid to have duplicate keys in YAML:

https://github.com/kaitai-io/kaitai_struct_formats/blob/2c318560d46a64a3338e531ff1540716dab9798c/media/magicavoxel_vox.ksy#L8-L9

We already have support for lists in doc-ref (kaitai-io/kaitai_struct#269), so this should be replaced with an array of two strings. Like this:

https://github.com/kaitai-io/kaitai_struct_fo

The mime type for Microsoft word looks wrong:
fleep\data.json: line 70
{"type": "document", "extension": "doc", "mime": "application/vnd.ms-excel", "offset": 0, "signature": ["D0 CF 11 E0 A1 B1 1A E1", "50 4B 03 04 14 00 06 00"]},

Should be:
application/msword

add check_integrity utility that can be called at key places, including Cooler instantiation

(if indexes are missing, cooler cli currently fails with uninformative errors, as below)

cooler coarsen --out test.cool
Traceback (most recent call last):
File "/home/gfudenberg/anaconda3/bin/cooler", line 11, in
load_entry_point('cooler', 'console_scripts', 'cooler')()
File "/

TrackUID is already documented as such
This SHOULD be kept the same when making a direct stream copy of the Track to another file.

I think a lot of IDs that are referenced in chapters, tags, attachments also need to be preserved. So we need to make sure they are marked as such (maybe an extension in our generic XML file).

For example, when accessing elements of a dimension, which is of type ndsize_t/NDSize, calculations can in theory overflow the precision and we thus "lose" information. Currently such situations are silently ignored. The question is how to deal with such cases.

Known occurrences:

• [src/Dimensions.cpp](https://github.com/G-Node/nix/blob/72d4e357766d78dafe52521786453793ee1b96a5/s

As of update 1.8, the .rm files are in a new format.

It lookes like instead of each file being indexed by the page number, the pages are now assigned a random UUID.

[root@remarkable 6b96d778-b6f5-458e-9b7d-649689706f37] ls
012f4a15-8cdb-4d44-aa02-05fd911873e6-metadata.json
012f4a15-8cdb-4d44-aa02-05fd911873e6.rm
0fe5e46a-51c1-4255-a062-c1333dd7eac9-metadata.json
0fe5e46a-51c1-4255-a

Please consider adding your library to vcpkg repository.
I have already prepared CONTROL file for you:

Source: libe57format
Version: 2.1
Description: C++ library implementing E57 point cloud format
Homepage: https://github.com/asmaloney/libE57Format
Build-Depends: xerces-c

And portfile.cmake:

include(vcpkg_common_functions)

vcpkg_from_github(
    OUT_SOURCE_PA

• would be added to groupList data
• in case of wwPDB data "missing atoms" would be in comparison to the corresponding CCD entry