Is so spartan that everyone need to encode dates somehow, to make a simple example. I think this are the base types (also, my experience with RDBMs and building a relational lang now, and always having troubles with cvs, json, and others formats in ETL kind-of-task):
- String
- Floats. Can be split Ints/Floats but stick to just Float is ok. However, make it Float64.
- Date(Time). And be ISO. Not ambiguity.
- Boolean
- Decimal64. This is a pet peeve of mine. A lot of data in the business space is about money, and floats are not ok. What if like in rebool $3.2 is decimal?
Then the composites.
ie: This is json + dates/decimal. And make a single encoding (utf8?).
Is insane that, for example, you save a CVS in excel and open it again and excel get lost, and can't parse it fine.
Apart from this, url, email, host, website, phone, cellphone, city, country, state are so common that maybe with a import like "!schema:common-fields" or something.
JSOn is a good example:
https://www.tutorialspoint.com/json/json_data_types.htm
Is so spartan that everyone need to encode dates somehow, to make a simple example. I think this are the base types (also, my experience with RDBMs and building a relational lang now, and always having troubles with cvs, json, and others formats in ETL kind-of-task):
- String
- Floats. Can be split Ints/Floats but stick to just Float is ok. However, make it Float64.
- Date(Time). And be ISO. Not ambiguity.
- Boolean
- Decimal64. This is a pet peeve of mine. A lot of data in the business space is about money, and floats are not ok. What if like in rebool $3.2 is decimal?
Then the composites.
ie: This is json + dates/decimal. And make a single encoding (utf8?).
Is insane that, for example, you save a CVS in excel and open it again and excel get lost, and can't parse it fine.
Apart from this, url, email, host, website, phone, cellphone, city, country, state are so common that maybe with a import like "!schema:common-fields" or something.