[w3ctag/design-reviews] Find the best terminology to restrict the usage of data urls (#635)

Ya ya yawm TAG!

The category ("dispute escalation") is a misnomer; this is more a help/clarification request.

I'm requesting the TAG express an opinion on a problem related to:

  - Name: EPUB 3.3
  - Specification URL: https://www.w3.org/TR/epub-33/
  - Explainer (containing user needs and example code): (in preparation)
  - GitHub issues (if you prefer feedback filed there): https://github.com/w3c/epub-specs/issues/1592
  - Primary contacts (and their relationship to the specification): @mattgarrish @dauwhe @iherman (editors)
  - The group where the work on this specification is: EPUB 3 WG
  - Links to major pieces of multi-stakeholder review or discussion of this specification: n/a
  - Links to major unresolved issues or opposition with this specification: n/a
  - Relevant time constraints or deadlines: July 2021

We recommend the explainer to be in Markdown.

Explanation of the issue that we'd like the TAG's opinion on:

"There is no final agreement in the WG on how to precisely formulate the restrictions on the usage of data-url-s. The [current formulation](https://w3c.github.io/epub-specs/epub33/rs/#confreq-rs-data-urls) relies on the top-level browsing contexts term but that may not be adequate (e.g., if the top level document is an SVG file)."

Cc @ylafon

-- 
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/635