- From: Jai Krishnan <notifications@github.com>
- Date: Wed, 29 Apr 2020 14:31:04 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 29 April 2020 21:31:17 UTC
> Could you explain why the HEIF container was used in comparison with other containers (WebP uses RIFF). How does this choice affect the use on the web? Benefits of the container design include compatibility and familiarity for developers, particularly those whose pipelines include uploads from mobile cameras. > So a bit of a blunt question based on what we discussed in today's call - this is based off of AVIF, which is not a royalty-free standard as we understand it. What was the technical background of the decision, and is there a path forward given the provenance of the core container format this is based off of? Re: provenance, the AVIF image file format describes the use of an AV1 bitstream with a subset of the ISO-BMFF container, i.e. the [MiAF](https://www.iso.org/standard/74417.html) constraints. Our view is the AVIF format would be available for use by open platforms like Chromium, in line with [AOM's position](http://aomedia.org/the-alliance-for-open-media-statement) on AV1 royalties. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/495#issuecomment-621475548
Received on Wednesday, 29 April 2020 21:31:17 UTC