dedicated types in what name space?

Dedicated types in the logical data model. Imagine json would suddenly gain support for integers. These integers would then have the same standing as the old data types (null, boolean, float, string, array, object). Unlike json where this can't happen, we can do this for hsdt. What I'm asking for in this thread: What types of things other than null, booleans, floats, strings, arrays, and objects should application devs have at their disposal?

Not thinking about this means accepting that the types provided by json form the best possible set of types, and everyone should only use those to build applications. Ssb currently restricts devs to them. But pretty much every developer who did not grow up in js-land would look at this at say "Wait a second, the fundamental datatype of every machine is the integer. A large subset of algorithmic problems consists of manipulating integers. Do you seriously expect me to build apps without integers? Sorry, but I'm leaving for ipfs".

There are some concerns with introducing new types, but for now I'd just like to survey which types might be sensible to have. Well, and I'd like to lobby for the inclusion of integers.