--===============0665557171== Content-type: multipart/alternative; boundary="Apple-Mail=_FB290BC0-2E91-4744-81D7-57F33822ABF0" --Apple-Mail=_FB290BC0-2E91-4744-81D7-57F33822ABF0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Without having read the spec in detail, the first thing I wonder is why = not use RSS for this purpose? That seems to be the de facto standard for = audio feeds (i.e. podcasts). This is dismissed in a cursory way in the = explainer. There=E2=80=99s some more detailed discussion in the issue = filed by the TAG: = , which I found = eventually. It seems like some of that should go in the Explainer. Second, it=E2=80=99s not clear to me if this spec has anything that = would need to be implemented in the browser engine. Rather, it provides = a format for metadata linked from the page, which can optionally be used = by the UA in some manner unrelated to processing of web content. Is that = correct? (Asking in part to know the right people to ask for an = opinion.) Third, and this is a minor thing, it seems strange that the spec (and = parts of its syntax) are called Media Feeds instead of Video Feeds, = since audio is explicitly out of scope. Perhaps audio is intended to be = added later. If so, that increases the value of aligning with how = podcasts are done today. > On Jun 17, 2020, at 2:48 PM, Becca Hughes = wrote: >=20 > Hi webkit-dev, >=20 > I would like to request an official position on Media Feeds. >=20 > Explainer: = https://github.com/WICG/media-feeds/blob/master/explainer.md = > Chrome Status: https://chromestatus.com/feature/5695114963845120 = > TAG review: https://github.com/w3ctag/design-reviews/issues/477 = >=20 > Thanks, > Becca > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev --Apple-Mail=_FB290BC0-2E91-4744-81D7-57F33822ABF0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

Without having read the spec in detail, = the first thing I wonder is why not use RSS for this purpose? That seems = to be the de facto standard for audio feeds (i.e. podcasts). This is = dismissed in a cursory way in the explainer. There=E2=80=99s some more = detailed discussion in the issue filed by the TAG: <https://github.com/beccahughes/media-feeds/issues/10>, = which I found eventually. It seems like some of that should go in the = Explainer.

Second, = it=E2=80=99s not clear to me if this spec has anything that would need = to be implemented in the browser engine. Rather, it provides a format = for metadata linked from the page, which can optionally be used by the = UA in some manner unrelated to processing of web content. Is that = correct? (Asking in part to know the right people to ask for an = opinion.)

Third,= and this is a minor thing, it seems strange that the spec (and parts of = its syntax) are called Media Feeds instead of Video Feeds, since audio = is explicitly out of scope. Perhaps audio is intended to be added later. = If so, that increases the value of aligning with how podcasts are done = today.


On Jun 17, 2020, at 2:48 PM, = Becca Hughes <beccahughes@chromium.org> wrote:

Hi webkit-dev,

I would like to request an official position on Media = Feeds.

Explainer: https://github.com/WICG/media-feeds/blob/master/explainer.md
Chrome Status: https://chromestatus.com/feature/5695114963845120
TAG review: https://github.com/w3ctag/design-reviews/issues/477

Thanks,
Becca
_______________________________________________
webkit-dev = mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

= --Apple-Mail=_FB290BC0-2E91-4744-81D7-57F33822ABF0-- --===============0665557171== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev --===============0665557171==--