René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`aem`  Date format not compatible with ECMA Script","articleBody":"Events produced by `aem` have the form:\r\n\r\n```\r\n{\r\n    \"event_id\": \"2e38cbbe-4426-468c-b5ff-a8940e3210a6\",\r\n    \"event\": {\r\n        \"@id\": \"urn:oeid:aem:779885b1-f2fa-480d-b0c0-5a93619c5d29\",\r\n        \"@type\": \"xdmCreated\",\r\n        \"activitystreams:published\": \"2021-03-16T10:54:47.037+01\",\r\n        \"activitystreams:to\": {\r\n            \"@type\": \"xdmImsOrg\",\r\n            \"xdmImsOrg:id\": \"B28447B65D88A19F0A495C33@AdobeOrg\"\r\n        },\r\n \r\n```\r\n...       \r\n\r\n\r\n \r\nUnfortunately, the JavaScript methods Date.parse() or new Date() cannot parse Date-Strings like that one:\r\n\r\n`2021-03-16T10:54:47.037+01 //ERROR!!`\r\n\r\n(even though it's proper ISO-8601) The correct format is \r\n\r\n`2021-03-16T10:54:47.037+01:00`\r\n \r\n\r\nWith the additional minute-denominator in the timezone (yes - there are half-hour time zones on the globe ..)\r\n\r\nWhat also is allowed is `2021-03-16T10:54:47.037Z`\r\nfor \"Zulu-time\" which is equivalent to \"+00:00\"\r\n\r\nNow we should assume that 90% of the receivers are implemented in I/O runtime and thus implemented in JS. So I think it's worth the effort fixing it.\r\n\r\nYou can argue, that this can easily be done with a regex in the client code... \r\nBUT: Most of the time I received valid events with \"Z\" timezone.. and my code worked perfectly well. \r\nUntil now, when I saw these \"incomplete\" \"+01\" showing up in the queue.. \r\nand my perfectly working code stopped working \r\n\r\nBTW: \"+01:00\" also is perfectly ISO-8601 compatible... so it should be safe to use that format instead.","author":{"url":"https://github.com/francoisledroff","@type":"Person","name":"francoisledroff"},"datePublished":"2022-04-07T15:14:12Z","url":"https://github.com/adobe/aio-lib-java/issues/103"}