rok commented on PR #41257: URL: https://github.com/apache/arrow/pull/41257#issuecomment-2061349391
Right, the `media_type` information would enable end users to interpret how data is encoded. Alternatively we could have one extension per endoding (JSON, YAML, etc) or say that JSON is special and only provide it as a canonical type. I'm ok either way actually, just proposing a more general approach. > By the way, the notion of a "generic" extension type meant to represent arbitrary third-party data is similar to the ["other / unsupported data type"](https://lists.apache.org/thread/8d5ldl5cb7mms21rd15lhpfrv4j9no4n) currently being discussed on the ML. @lidavidm @westonpace > > I don't see any reason to restrict such an "other" type to text data. Here we would limit ourselves to text based IANA registered media types. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
