westonpace commented on code in PR #41257:
URL: https://github.com/apache/arrow/pull/41257#discussion_r1585081438
##########
docs/source/format/CanonicalExtensions.rst:
##########
@@ -251,6 +251,27 @@ Variable shape tensor
Values inside each **data** tensor element are stored in
row-major/C-contiguous
order according to the corresponding **shape**.
+.. _json_extension:
+
+JSON
+====
+
+* Extension name: `arrow.json`.
+
+* The storage type of this extension is ``StringArray`` or
+ or ``LargeStringArray`` or ``StringViewArray``.
+ Only UTF-8 encoded JSON is supported.
+
+* Extension type parameters:
+
+ This type does not have any parameters.
+
+* Description of the serialization:
+
+ Metadata is either an empty string or a JSON string with an empty object.
+ In the future, additional fields may be added, but they are not required
+ to interpret the array.
Review Comment:
I think I agree with Ian that stricter is better. It's fine for different
components within a system to agree they want to support a wider set of values.
However, once data leaves a solution, it should assume that most components
will only be processing the to-spec JSON. This document is primarily about
interchange and so should be concerned with the latter case (data leaving a
solution to be consumed by some unknown component).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
