- From: cynthia <notifications@github.com>
- Date: Tue, 04 Sep 2018 06:13:28 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 4 September 2018 13:14:50 UTC
Takeaway from last meeting: https://github.com/w3ctag/meetings/blob/gh-pages/2018/telcons/08-28-minutes.md Summarized, the use cases seem valid. We have some general concerns around the security model (which has been improved, awaiting access to the updated spec) - particularly on whether or not this context should have access to "powerful features" which are only accessible in secure context, and whether or not this is a secure context, what the origin is, which we would love to have clarified in the updated spec. Additionally, putting HTTP/packaging equivalent in the scope of a media container as with the current design looks like it could have some future scalability/flexibility issues - we'd love to see if a singular brand that specifies a web package, which can then be run would be an alternate option forward. I missed the "Advance signaling of MPEG media and containers in web communication environments" in the review request, will look at that once we have access to the documents. Please let us know when the updated documents have been made available, and we will revisit this review. -- 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/285#issuecomment-418362126
Received on Tuesday, 4 September 2018 13:14:50 UTC