'Re: [webkit-dev] Request for position on Media Feeds'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       webkit-dev
Subject:    Re: [webkit-dev] Request for position on Media Feeds
From:       Maciej Stachowiak <mjs () apple ! com>
Date:       2020-06-17 23:09:53
Message-ID: 0AB38DE3-1648-42F7-97C8-96DC6C765490 () apple ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

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's 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's 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 \
> <https://github.com/WICG/media-feeds/blob/master/explainer.md> Chrome Status: \
> https://chromestatus.com/feature/5695114963845120 \
> <https://chromestatus.com/feature/5695114963845120> TAG review: \
> https://github.com/w3ctag/design-reviews/issues/477 \
> <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

[Attachment #5 (unknown)]

<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body \
style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" \
class=""><div class=""><br class=""></div>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's some \
more detailed discussion in the issue filed by the TAG: &lt;<a \
href="https://github.com/beccahughes/media-feeds/issues/10" \
class="">https://github.com/beccahughes/media-feeds/issues/10</a>&gt;, which I found \
eventually. It seems like some of that should go in the Explainer.<div class=""><br \
class=""></div><div class="">Second, it's 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.)</div><div class=""><br class=""></div><div class="">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.</div><div \
class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun \
17, 2020, at 2:48 PM, Becca Hughes &lt;<a href="mailto:beccahughes@chromium.org" \
class="">beccahughes@chromium.org</a>&gt; wrote:</div><br \
class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi webkit-dev,<div \
class=""><br class=""></div><div class="">I would&nbsp;like to request an official position on \
Media Feeds.</div><div class=""><br class=""></div><div class="">Explainer:&nbsp;<a \
href="https://github.com/WICG/media-feeds/blob/master/explainer.md" target="_blank" \
class="">https://github.com/WICG/media-feeds/blob/master/explainer.md</a></div><div \
class="">Chrome Status:&nbsp;<a href="https://chromestatus.com/feature/5695114963845120" \
target="_blank" class="">https://chromestatus.com/feature/5695114963845120</a></div><div \
class="">TAG review:&nbsp;<a href="https://github.com/w3ctag/design-reviews/issues/477" \
target="_blank" class="">https://github.com/w3ctag/design-reviews/issues/477</a></div><div \
class=""><br class=""></div><div class="">Thanks,</div><div class="">Becca</div></div> \
_______________________________________________<br class="">webkit-dev mailing list<br \
class=""><a href="mailto:webkit-dev@lists.webkit.org" \
class="">webkit-dev@lists.webkit.org</a><br \
class="">https://lists.webkit.org/mailman/listinfo/webkit-dev<br \
class=""></div></blockquote></div><br class=""></div></body></html>

_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

[prev in list] [next in list] [prev in thread] [next in thread] 