{"action":"created","issue":{"url":"https://api.github.com/repos/FasterXML/jackson-databind/issues/552","labels_url":"https://api.github.com/repos/FasterXML/jackson-databind/issues/552/labels{/name}","comments_url":"https://api.github.com/repos/FasterXML/jackson-databind/issues/552/comments","events_url":"https://api.github.com/repos/FasterXML/jackson-databind/issues/552/events","html_url":"https://github.com/FasterXML/jackson-databind/pull/552","id":43241135,"number":552,"title":"iso 8601 date format","user":{"login":"geronimo-iia","id":352507,"avatar_url":"https://avatars.githubusercontent.com/u/352507?v=3","gravatar_id":"","url":"https://api.github.com/users/geronimo-iia","html_url":"https://github.com/geronimo-iia","followers_url":"https://api.github.com/users/geronimo-iia/followers","following_url":"https://api.github.com/users/geronimo-iia/following{/other_user}","gists_url":"https://api.github.com/users/geronimo-iia/gists{/gist_id}","starred_url":"https://api.github.com/users/geronimo-iia/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geronimo-iia/subscriptions","organizations_url":"https://api.github.com/users/geronimo-iia/orgs","repos_url":"https://api.github.com/users/geronimo-iia/repos","events_url":"https://api.github.com/users/geronimo-iia/events{/privacy}","received_events_url":"https://api.github.com/users/geronimo-iia/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2014-09-19T13:59:24Z","updated_at":"2015-05-20T18:25:35Z","closed_at":"2014-09-23T16:55:25Z","pull_request":{"url":"https://api.github.com/repos/FasterXML/jackson-databind/pulls/552","html_url":"https://github.com/FasterXML/jackson-databind/pull/552","diff_url":"https://github.com/FasterXML/jackson-databind/pull/552.diff","patch_url":"https://github.com/FasterXML/jackson-databind/pull/552.patch"},"body":"Hello,\r\n\r\nAfter reading several post about iso 8601 date format,( like this one http://www.w3.org/TR/NOTE-datetime for example), I think that it could be easier to parse iso 8601 date if we could use both \"strict standard\" and short format.\r\n\r\nWe could parse format according this: \r\n[yyyy-MM-dd|yyyyMMdd][T(hh:mm[:ss[.sss]]|hhmm[ss[.sss]])]?[Z|[+-]hh:mm]]\r\n\r\nFor example:\r\n2007-08-13T19:51:23.2Z\r\n20070813T19:51:23Z\r\n2007-08-13T195123Z\r\n2007-08-13T19:51Z\r\n20070813T19:51Z\r\n20070813Z\r\n\r\nI hope it can help a little,\r\n\r\nThanks for you're job, time \r\n\r\nBest Regards\r\n\r\nJérôme\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/FasterXML/jackson-databind/issues/comments/103986473","html_url":"https://github.com/FasterXML/jackson-databind/pull/552#issuecomment-103986473","issue_url":"https://api.github.com/repos/FasterXML/jackson-databind/issues/552","id":103986473,"user":{"login":"cowtowncoder","id":55065,"avatar_url":"https://avatars.githubusercontent.com/u/55065?v=3","gravatar_id":"","url":"https://api.github.com/users/cowtowncoder","html_url":"https://github.com/cowtowncoder","followers_url":"https://api.github.com/users/cowtowncoder/followers","following_url":"https://api.github.com/users/cowtowncoder/following{/other_user}","gists_url":"https://api.github.com/users/cowtowncoder/gists{/gist_id}","starred_url":"https://api.github.com/users/cowtowncoder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cowtowncoder/subscriptions","organizations_url":"https://api.github.com/users/cowtowncoder/orgs","repos_url":"https://api.github.com/users/cowtowncoder/repos","events_url":"https://api.github.com/users/cowtowncoder/events{/privacy}","received_events_url":"https://api.github.com/users/cowtowncoder/received_events","type":"User","site_admin":false},"created_at":"2015-05-20T18:25:35Z","updated_at":"2015-05-20T18:25:35Z","body":"@newyankeecodeshop I am not sure which way to go with this: while I can see your argument, it is also true that since in Java date/time values are typically stored as \"milliseconds-since-epoch\" notation, and thereby value of a date-only value may well change depending on timezone information.\r\nPut another way: there is difference between date-only and date-time-for-midnight short cut. And it may not be obvious which usage is in effect.\r\n\r\nBut the point about ISO-8601 spec and RFC would be valid; if they suggest use of timezone offset / 'Z' is not legal then it probably was not a good idea to allow it.\r\n\r\nAnd then again, if such usage is wide-spread, we have to balance inter-operability (of being more liberal in accepting values, conservative in what we output) and standards-compliancy.\r\n\r\nWhat do you think would be the right thing to do, considering that this behavior is included in 2.5.0?\r\n"}}