Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFqEp-0002NB-1j for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Jan 2023 05:34:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pFqEn-0005CS-Lq for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Jan 2023 05:34:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFqEn-0005CJ-As for pgsql-hackers@lists.postgresql.org; Thu, 12 Jan 2023 05:34:53 +0000 Received: from mout.gmx.net ([212.227.15.19]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFqEl-0007ju-4d for pgsql-hackers@lists.postgresql.org; Thu, 12 Jan 2023 05:34:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1673501688; bh=ET81QBive4lYwDJVJ/Vbo8QgmV+tpt6CT28KdTaqJW0=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From:In-Reply-To; b=GDcjw9iv/AdyUwcdyPQDblsLuhqi7utinED4vdsSlMp6GK/B7d0fogP2lLA6pYo7c JQ7nDe9cXOOmDw4uDhRa6Y0seLR1E7hLIo5kieQbo5Ny5FokHvTgr2iSYfKp2G5+Cq Tcvu2bvQKlZ2fhkIreF72veKEVox+VxazlWj04zM8ROCr8yT+sNvkaIrbk80bxEziZ VukzAHDPZNWy73EKLH5TpXDqd+FumyLvrurghSAD/wZcMsG0A9YODbWJYmXMRcOJ6W sv5yfu2Sz7FtEsu1fktR68sLhKMu0lKvXF3SiaS+6EapZ3pvamS2AkwnonQqI9CbKs HBVs3DqSSoocw== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from [192.168.178.42] ([91.64.168.249]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MBDnI-1p3Di20Ies-00Cktt; Thu, 12 Jan 2023 06:34:48 +0100 Message-ID: Date: Thu, 12 Jan 2023 06:34:44 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: pgsql: Doc: add XML ID attributes to and tags. To: Tom Lane , Peter Eisentraut Cc: pgsql-hackers@lists.postgresql.org References: <56f62f5e-86d6-70d0-2d5a-49e1480e3c0b@enterprisedb.com> <769446.1673478332@sss.pgh.pa.us> From: Brar Piening In-Reply-To: <769446.1673478332@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:KniHfbzIigOzSOQ3gahUVJgkrc44KMtkW2tkdM4ky2qNnBCzjPO LwODsE5mxROvmj42oG3RRPldqF+ZOqz1qRlxWZ+Hm/8guoTbeGtHtmYSVpLH/NHXwjRTLlI 0ng97MgSWMwXhp9+86jyEyprC97CcxgjLrcug9RPYfmAX4KcSpfBv9gjpJSTjwWXRLlDz2j Jt2l33LpbSAEA7e3GkgKA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:U3h2d40Po7E=;qz4Vr2KcoWh/4FY+l6q3n6Q4hLv kOE9GWjex0U4+XpX8OKoLQ6wTgwjbBPH29G/aEC0jlMNkA7+36jeN/wdy/LAStqmZv8FB4UUw MqQ00SkoS7OGb8qdgaOjEoYpBJET8sj68xvhrEp9j7HPpS9tTzmn4EkDnAXsoO/niaBBoKtf6 BpQz1HHmvrx6fwP8QFmjZU3skX5vqf+Xf47ybxEyRbLgSgdg29I3HF/rj3jBEM4YuJOzLIyei Pna1mmz5q/hYShH8A2/kILdg8lAeVSkv40cLAoh+BaoQE7M6OsHgpITOvcpFZI61t2khqzWWc HJKx1fWxF4zStoaqwV4xX8Vaj+sb7oXf86yKmQoXp3fagAG6wJWI2tmLPggDdpSQMHzfyYfRN Suaihpz/2g8MsQzybASFLViE1T6u99iSmzTUJSFzeZgcnMfIzv+60kOfYo2YkNoaF2XPEz5eA zPFLb68rNszl/3aZnzrdfZHVUm96Qn278YwpQiIZuXAoTsvtlfRjKR+lDfgjoMuxk4xsufZL9 ADgE/tmVLlbagAVmEzbSOWO4BGmnFEx0PWSbGL2ZxzegoyL7uhmXWDCfj9OpOvjsXhs5yQSjZ 8sJ9mAjrE1w9xYbVuIqSdmPjJn1h88Jyd13E3wC49pyRUa2oKioZcwHPOh3WMPEuIZxXf0tcC vKpFS4LBE4zwehbullUX6hdCwUJCbckVpBnQYPdTeiIUP1CFs+cCvK9kuF9gTCIxzNyweTzL+ TxQNpigKM2vRGm6/CgmU/NXCeXxmS1LgGgYhr09dITR0JtbtXtK4xMeTbLJxEpG0paJi3Y7bE 4z3D8Yb6mJkOx8pk9rrTSz6XPUWZ7ip13RAkUqsRFFzwUII8Z/YI3s8kGqKoGoO6ezoezLUaK fqJlDC25JbfC1syg9BbiJCEFFDyJUY79oulRcXTGyoRzOEqEZxPS+J/GMeSS+aMdGq2KNyiEV 1ypikZ5/be3s34KGYy190M77FF4= List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12.01.2023 at 00:05, Tom Lane wrote: > Peter Eisentraut writes: >> Any reason the new ids in create_database.sgml deviate from the normal >> naming schemes used everywhere else? Is it to preserve the existing >> create-database-strategy? Maybe we should rename that one and make the >> new ones consistent? I don't remember every single choice I made but the general goal was to at least stay consistent within a varlist/[sub]section/file/chapter and *never* change pre-existing ids since somebody may already be pointing to them. After all it is just an identifier that is supposed to be unique and should not hurt our aesthetic feelings too much. The consistency is mostly because we tend to like it and maybe also to avoid collisions when making up new ids but I doubt that anybody will ever try to remember an id or infer one form knowledge about the thing it should be pointing at. I consider it a pretty opaque string that is meant for copy-paste from a browser to some editing window. It is all in our head and as a matter of fact we could be using UUIDs as Ids and save us from any further consistency issues. It's just that they look so ugly. > You'd have to ask Brar that, I didn't question his choices too much. > > I have no objection to changing things as you suggest.I'm hesitant to > rename very many pre-existing IDs for fear of breaking peoples' bookmark= s, > but changing create-database-strategy doesn't seem like a big deal. Personally I'd only d this for ids that haven't been "released" as official documentation (even as "devel" since the new things tend to attract more discussions and probably linking). I very much consider URLs as UI and go long ways to keep them consistent (HTTP 3xx is a friend of mine) as you never know who might be pointing at them from where and making them a moving target defeats their purpose and probably hurt more than some inconsistency. Regards, Brar