The key word in stylized-text is "style" and that word seems to go past being purely informational (what does it mean) to being somewhat presentational (what does it look like).
I propose that we rename this hint to emphasized-text to distance the hint from presentational contexts and better express its intent in informational contexts – to add emphasis to text, or de-emphasis in the case of --foo--, in a Lynx+JSON document.
In addition to that change, the examples would need to be rewritten to use informational terms rather than presentational terms. For example (and this is not a proposal for documentation, but just an illustration of how to remove the presentational terms of italics, bold, strikethrough, etc.):
The key word in
stylized-text
is "style" and that word seems to go past being purely informational (what does it mean) to being somewhat presentational (what does it look like).I propose that we rename this hint to
emphasized-text
to distance the hint from presentational contexts and better express its intent in informational contexts – to add emphasis to text, or de-emphasis in the case of--foo--
, in a Lynx+JSON document.In addition to that change, the examples would need to be rewritten to use informational terms rather than presentational terms. For example (and this is not a proposal for documentation, but just an illustration of how to remove the presentational terms of italics, bold, strikethrough, etc.):
--foo--
__foo__
*foo*
**foo**
***foo***