Le 17/08/2022 à 18:45, Joris Van den Bossche a écrit :
+1 on the overall proposal, documenting those in a central place sounds
good to me.

On Wed, 17 Aug 2022 at 18:10, Antoine Pitrou <anto...@python.org> wrote:


....

* The specification text to be added *must* follow these requirements

1) It *must* have a well-defined name starting with "ARROW:"


One remark on the specific naming convention: our documentation (
https://arrow.apache.org/docs/format/Columnar.html#extension-types)
currently recommends this kind of namespacing as well, but uses a
"myorg.name_of_type" pattern as example. For the extension types that I am
aware of (helped implementing), we followed that (for example, in pandas we
define "pandas.interval" and "pandas.period" extension types, and in
geoarrow
<https://github.com/geopandas/geo-arrow-spec/blob/main/extension-types.md>
we have "geoarrow.point", "geoarrow.polygon", etc).
I don't have a strong opinion here, but so we can also continue using that
pattern for the canonical types as well: "arrow.<type>" (or
"org.apache.arrow.<type>" as mentioned during the sync meeting).

Point taken. I will adapt the proposal to the "org.apache.arrow." convention.

Regards

Antoine.

Reply via email to