-
I am trying to output ISO 8601 dates surrounded by double quotes. This seems to be very difficult or impossible. What I want is this output:
```
followers,account_id,created
7346950,13460080,"2014-10…
-
Some gedcom files have dates formatted in ISO 8601 format. Some genealogy software, for example Gramps, parses this correctly.
It would be nice if python-gedcom can parse datestrings to date objects,…
-
The `created` field in the JSON payload for edition history (ie `?m=history`) isn't correctly formatted.
### Evidence / Screenshot (if possible)
![Screen Shot 2023-02-10 at 2 59 25 PM](https://use…
-
### eDocs volgnummer
2024006271
### Korte probleem omschrijving
De huidige implementatie van de elementen van het type datumtijd of tijd in het berichtenverkeer staan geen tijdzone toe. Dit is in d…
-
### Reproduction steps:
1. Set your timezone to London timezone (Before 1848 in London the time offset was UTC -0:01:15, see https://www.timeanddate.com/time/zone/uk/london)
2. Run the following cod…
-
Current logic for Authentication-Results header is based on [RFC 7601](https://tools.ietf.org/html/rfc7601).
There exist a newer [RFC 8601](https://tools.ietf.org/html/rfc8601). No analysis yet don…
-
-
_Jeremy John Reeder on 2015-05-13T21:42:22Z says:_
"2017" is a valid ISO-8601 date, although it's not listed among [Taskwarrior's supported date formats|http://taskwarrior.org/docs/dates.html]. Tas…
-
Currently, _Common_ and _Features_ reference http://www.opengis.net/def/uom/ISO-8601/0/Gregorian as the temporal reference system.
However, that does not resolve with http://www.opengis.net/def/crs…
-
According to Wikipedia, for an ISO 8601 time:
>Decimal fractions may be added to any of the three time elements. However, a fraction may only be added to the lowest order time element in the repres…