Inconsistencies when defining values `int` and `uint` on the `dtype` specification key

[ehennestad]

I find the following inconsistencies in defining int and uint for the dtype key in the HDMF/NWB schema specifications

HDMF Schema Language

• In the hdmf-schema-language docs
  uint -> uint8
int -> int8

HDMF

• In the DtypeHelper class of hdmf.spec namespace
  https://github.com/hdmf-dev/hdmf/blob/99ce39e96cab7330d37e739efd0f6451eb3da1f0/src/hdmf/spec/spec.py#L25-L43
  uint -> uint32
int -> int32

• In the ObjectMapper of the hdmf.build namespace
  https://github.com/hdmf-dev/hdmf/blob/99ce39e96cab7330d37e739efd0f6451eb3da1f0/src/hdmf/build/map.py#L345-L369
  uint mapping is missing

NWB Schema language

• In the nwb-schema-language docs
  int -> int32
uint is missing

Related issues:

• uint missing from dtypes NeurodataWithoutBorders/nwb-schema#254
• Definition of dtype int (int=int32) in documentation is inconsistent with HDMF (int=int8) NeurodataWithoutBorders/nwb-schema-language#13

[rly]

Thanks for documenting this. Sorry, this is a case of us not working fast enough to 1) release the latest 3.0.0 version of the schema language (the change was here), 2) pull updates from the hdmf-schema-language into nwb-schema-language, and 3) support it in HDMF . I don't remember what the hold up was, so let me investigate that now...

[ehennestad]

Thanks for clarifying!