Re: [w3ctag/design-reviews] Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819)

There's either a grand misunderstanding in this issue (likely our fault) or a whole new principle being described for how all DOM and HTML elements should be described in schema.org terms. The second one strikes me as unlikely, as it would suggest that all extensions to HTML or the Web App Manifest spec should be described in (or by) schema.org entity types, and that the TAG is proposing to work with all proposers of DOM or HTML extensions to develop such a taxonomy. That's a big lift which I might actually support in principle, but is not enunciated clearly in this tread, is not in the Design Principles, and has no precedent in the platform.

Assuming that's *not* what we're doing, the history of this design is more illustrative of the goal: to allow dynamic configuration of stand-alone window UI in ways that are not generally part of either an indexer's data set, and which were initially proposed as  DOM API in the form of `document.subtitle`, with the HTML meta tag added only for consistency. In common use, we expect the subtitle to be set and changed *only* from script. This may have been unclear in the explainer(s), which is our fault.

Given that the TAG feedback is now far afield of this goal, and quite late to boot, it's somewhat vexing that the goal has been lost. Is it possible @diekus (and perhaps myself) to join an upcoming call to work through the feedback you've proposed here?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/819#issuecomment-2206444084
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/819/2206444084@github.com>