Rob Marrowstone

An observation is that the `TimestampBuilder` could be refactored to take the components of the `Decimal` for fractional seconds. This would preserve the invariants such that the Text parser and...

It's not clear to me that the right answer is to disallow "offset-aware" dates. The W3C XSD date type allows an offset, for example, and the Java SE DateTimeFormatter parses...

Another example: `(2000T -2001T)` Is not valid per the ANTLR grammar (Ion doesn't allow negative timestamps), but it _could_ be parsed as: `(2000T '-' 2001T)`

To make a question explicit: the Spec says "real values" as to whether the intention was "real numbers" (in the mathematical sense) or "real values" (as in not-null?) is not...

Has an option flag been considered? For example: ``` ion --beta schema validate ... ``` Where the `--beta` (or `--experimental`?) flag would enable beta functionality but does not prevent production...

Hi! It is true that Ion is a superset of JSON, but it doesn't follow that JSON Arrays should necessarily be treated as Rows/Structs by the Ion SerDe. I understand...

For context, this appears to be a follow-up from https://github.com/amazon-ion/ion-python/issues/362 My suggestion there was to use the `IonPyValueModel.STRUCT_AS_STD_DICT` which should result in Ion Structs deserializing to `IonPyStdDict` objects (which inherit...

This isn't really a bug with ion-python. In the Ion text format `1` is an Integer and `1.` is a Decimal, see: https://amazon-ion.github.io/ion-docs/docs/spec.html Per the DynamoDB Import Docs: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/S3DataImport.Format.html#S3DataImport.Requesting.Formats.Ion They...

I would further advise that for your production code you serialize your Ion as Binary for the imports. Obviously the text format is great for debugging and developing, but the...

Sadly it does look like they only support the Text format, so that was some bad advice, sorry. It would be more optimal if they supported the binary format, but...