I lack the background on why that odd "avro/binary" style was chosen. Registering an IANA media type for Avro and supporting it in the different implementations sounds like an excellent idea!
Other Apache projects have registered IANA types like 'application/vnd.apache.thrift.binary' or 'application/vnd.apache.arrow.stream' but I have seeing "application/avro" used in many projects in the wild like https://github.com/apache/camel/blob/2f11b3147d4d1d53bf59ffd54ac098f674c29efe/core/camel-api/src/main/java/org/apache/camel/spi/MimeType.java#L31-L34 It should not be a major issue of course to support this (we would need to update the spec and the language specific IPC implementations to support the new type + deprecate the "avro/binary" media type. So far I have never seeing anyone mention registering a proper media type for Avro. Anyone see any issues (that I might be missing) if we do this? What do others think? Other ideas/comments? Ismaël On Mon, Jan 8, 2024 at 4:32 PM Clemens Vasters <cleme...@microsoft.com.invalid> wrote: > The spec states that the media type for Avro should be "avro/binary, which > is in conflict with the common pattern of the IANA media type registry and > Avro is also not registered there. > > In the CNCF CloudEvents and CNCF xRegistry efforts we take Avro > dependencies and we also take dependencies on Avro in Microsoft Azure and > Microsoft Fabric, and that aspect irks me. > > Has there ever been an effort to register the media type formally? > > Thank you > Clemens > > cleme...@microsoft.com >
