Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r4yUl-00BBTE-AT for pgsql-docs@arkaria.postgresql.org; Mon, 20 Nov 2023 07:14:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r4yUi-006F11-Pp for pgsql-docs@arkaria.postgresql.org; Mon, 20 Nov 2023 07:14:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r4yUi-006F0t-Hj for pgsql-docs@lists.postgresql.org; Mon, 20 Nov 2023 07:14:56 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r4yUg-007NR3-4o for pgsql-docs@lists.postgresql.org; Mon, 20 Nov 2023 07:14:55 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 112135C0095; Mon, 20 Nov 2023 02:14:53 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 20 Nov 2023 02:14:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to; s=fm3; t=1700464493; x=1700550893; bh=O60C9JtbhtGbLsy724eNZZWzD EDheUZxOfTPErDVeH0=; b=IDRPCoaczrTcQivK0+nwASjFjKMcr+1HvCl0b/iAW iE46O8XFr42Rn/aa1HXAMpmnFpkpIxZISR6QGvVXxdwoC9jqJjI+Kk+y+LeUlr3g 790W2KzkZJn8R6/m8eI0y6/mafs/muwBSv7BdjHsVIbG3WLq0XGH1480xzrpL891 Tjh08Q9vxu02PsD5tIbOZLVUiF5xSdDkreTFDOcDo6Gwz9SFct7Yng24GjVQ39EH fy0QooNhGeHDqdU5bcWImAHrFhXmpXGBIwsMfGygfxN4MXMZc4Vf29fWBavjadxH 6lPaXPYN+bNG32kRKYcGJ4r5WF4sVXip4i5wpKz4FabXw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1700464493; x=1700550893; bh=O60C9JtbhtGbLsy724eNZZWzDEDheUZxOfT PErDVeH0=; b=3c/hL4JfJ0GDkUsokZaJX3Qu3OdfuJ2n7Ztpr7AXwPAn89Pwk0N oztEV3JC9EfhdQ1/ykU7hr7vEvIt7bCDBrvPxulfJsUFpeuLjRB1RNIXv5FVM+ju /wscij50rp5RF39V59muf2duAIU1nsP4e0NnV2FOob+D4igcDFxFCToK/TXls/Ys czKGEGRIB1rE6nCOyv/TQkipZ/4pMAkIVpxfj+RbNoeooNxS4lR4XBkiKNU/+ldp +6DCtB0GQlCAhAJlQa60XqAfkLsINrJ5FW+ewzxNnjV7rac3otfY7Sw+5y1Pm1r6 69Ebsie8qgxtaJO12rC3p2Kx7WrDhVjhWsw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudeghedguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttddvjeenucfhrhhomheprfgv thgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorh hgqeenucggtffrrghtthgvrhhnpefgjedthfekfedtuefgieelheetleejgefhueeltdfh ueetvdffudekfeejhfegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 20 Nov 2023 02:14:51 -0500 (EST) Message-ID: Date: Mon, 20 Nov 2023 08:14:50 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: T is a mandatory date time separator in RFC3339 but documentation states differently Content-Language: en-US To: Erik Wienhold , Tom Lane Cc: =?UTF-8?Q?Roman_Fro=C5=82ow?= , pgsql-docs@lists.postgresql.org References: <7njdkzeco47heg6tglzsm5wmmbb56vd66f7pta6gazb2k52viu@av3wruqnylpp> <2037453.1699892596@sss.pgh.pa.us> <408aa3cd-0085-41c3-855c-3d51a1bc55d3@eisentraut.org> <78c14be8-47f2-4624-9d98-3730b492977e@eisentraut.org> <2657881.1700059603@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 19.11.23 21:34, Erik Wienhold wrote: > * Making explicit references to ISO 8601:2004 where section numbers are > referenced. Mostly in source comments but also a couple of places in > the docs. This is about avoiding confusion as ISO 8601:2019 has been > published since then, with different section numbers[1]. The pre-2004 > editions also have different section numbers. References to general > ISO 8601 concepts (e.g. week numbers) are left unchanged because those > are not tied to any particular edition. Maybe we should change the references to the 2019 edition instead?