Shall we create a JIRA issue to memorialize this task?
On Thu, Dec 12, 2019 at 1:16 AM Micah Kornfield <emkornfi...@gmail.com> wrote:
>
> Yeah, I was thinking to wait for the actual formats to become "official",
> but I agree the names won't change.
>
> On Thu, Dec 5, 2019 at 9:55 PM Sutou Kouhei <k...@clear-code.com> wrote:
>
> > I think that we don't need to wait for 1.0.0. Because we
> > don't change existing format names. ("streaming" and "file"
> > aren't changed.)
> >
> > In <CAK7Z5T99dEbE5BUJjQ73MDezZCGTOB2SpBWBTD7R=iodb8n...@mail.gmail.com>
> > "Re: MIME type" on Sun, 1 Dec 2019 20:45:43 -0500,
> > Micah Kornfield <emkornfi...@gmail.com> wrote:
> >
> > >>
> > >> Should we register our MIME types to IANA?
> > >
> > > Are there any downsides to doing this? should we wait for 1.0.0?
> > >
> > > On Thu, Nov 21, 2019 at 5:04 AM Sutou Kouhei <k...@clear-code.com> wrote:
> > >
> > >> I found Apache Thrift registers the following MIME types:
> > >>
> > >> * application/vnd.apache.thrift.binary
> > >> * application/vnd.apache.thrift.compact
> > >> * application/vnd.apache.thrift.json
> > >>
> > >> https://www.iana.org/assignments/media-types/media-types.xhtml
> > >>
> > >> Thrift uses "vnd.apache." prefix[1].
> > >>
> > >> [1] https://tools.ietf.org/html/rfc6838
> > >> > Vendor-tree registrations will be distinguished by the leading facet
> > >> > "vnd.". That may be followed, at the discretion of the registrant,
> > >> > by either a media subtype name from a well-known producer (e.g.,
> > >> > "vnd.mudpie") or by an IANA-approved designation of the producer's
> > >> > name that is followed by a media type or product designation (e.g.,
> > >> > vnd.bigcompany.funnypictures).
> > >>
> > >> vnd.apache.thrift.binary was registered at 2014-09-09:
> > >>
> > >>
> > >>
> > https://www.iana.org/assignments/media-types/application/vnd.apache.thrift.binary
> > >>
> > >> Should we register our MIME types to IANA?
> > >>
> > >> It seems that Apache Thrift uses application/x-thift (typo?)
> > >> before Apache Thrift registers these MIME types.
> > >>
> > >> > The application/x-thift media type is currently used to describe
> > multiple
> > >> > formats/protocols. Communications endpoints need to the
> > format/protocol
> > >> > used, so this media type should be used preferentially when it is
> > >> > appropriate to do so.
> > >>
> > >> In <bb1f0e75-6255-8d3e-085c-ffd26b654...@python.org>
> > >> "Re: MIME type" on Wed, 20 Nov 2019 12:01:54 +0100,
> > >> Antoine Pitrou <anto...@python.org> wrote:
> > >>
> > >> >
> > >> > If it's not standardized, shouldn't it be prefixed with x-?
> > >> >
> > >> > e.g. application/x-apache-arrow-stream
> > >> >
> > >> >
> > >> > Le 20/11/2019 à 08:29, Micah Kornfield a écrit :
> > >> >> I would propose:
> > >> >> application/apache-arrow-stream
> > >> >> application/apache-arrow-file
> > >> >>
> > >> >> I'm not attached to those names but I think there should be two
> > >> different
> > >> >> mime-types, since the formats are not interchangeable.
> > >> >>
> > >> >> On Tue, Nov 19, 2019 at 10:31 PM Sutou Kouhei <k...@clear-code.com>
> > >> wrote:
> > >> >>
> > >> >>> Hi,
> > >> >>>
> > >> >>> What MIME type should be used for Apache Arrow data?
> > >> >>> application/arrow?
> > >> >>>
> > >> >>> Should we use the same MIME type for IPC Streaming Format[1]
> > >> >>> and IPC File Format[2]? Or should we use different MIME
> > >> >>> types for them?
> > >> >>>
> > >> >>> [1]
> > >> >>>
> > >> https://arrow.apache.org/docs/format/Columnar.html#ipc-streaming-format
> > >> >>> [2]
> > https://arrow.apache.org/docs/format/Columnar.html#ipc-file-format
> > >> >>>
> > >> >>>
> > >> >>> Thanks,
> > >> >>> --
> > >> >>> kou
> > >> >>>
> > >> >>
> > >>
> >
