Axel Huebl

(Sorry, clicked wrong button.)

As reasoned above, we do not have a file format that does not support complex in our production workflows. Due to the reasons above (maintenance, reference implementations, upgrades, etc.) I...

Thank you for documenting your ideas! I think moving geometry generally into an extension would be marvelous, even independent of the special spatial case of `thetaMode`. Such an extension would...

Thank you for the issue! Can you elaborate on "particle positions are recorded at constant longitudinal position". Wouldn't these positions be stored over a iteration (snapshot) that can be referred...

That sounds like a plan. In case we get #141 implemented in 2.0 this might be able to be expressed in the base standard and we might not need this...

side note: typo in `timeUnitSI`: "conversion factor"

Good catch, I was thinking the same thing last week when someone posted about ISO 8601.

Out of the [extended formats](https://www.w3.org/TR/NOTE-datetime) in ISO 8601, should we go for ``` Complete date plus hours, minutes and seconds: YYYY-MM-DDThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00) ``` or ``` Complete date plus hours,...

### Proposal - add both as `optional` to the base standard record definition ### Problems we need to address - the symbol is kind of doubled with the record name...

As a note: it is also easily possible for a data reader of the base standard + domain specific extension to map specific symbols from record names during post-processing. The...