Default text direction example and assertion #1437
Conversation
|
I have checked the correctness of the text with @FadySalama . This adds a MAY assertion by removing its editor's note and adds a corresponding example. |
index.html
Outdated
|
|
||
| <p> | ||
| Strings on the Web [[?STRING-META]] suggests | ||
| both strong-first and language-based inferencing as means |
index.html
Outdated
| @@ -3022,6 +3008,49 @@ <h3>Human-Readable Metadata</h3> | |||
| } | |||
| </pre> | |||
|
|
|||
|
|
|||
| <p> | |||
| Strings on the Web [[?STRING-META]] suggests | |||
There was a problem hiding this comment.
We don't actually suggest both first-strong and inference from language tags. We actually recommend metadata falling back to first-strong. About language tags we say:
This approach is only recommended as a workaround for situations that prevent the use of metadata.
Because you are using JSON-LD, you have metadata for the document as a whole and for individual string values (notably title and description). What you don't have is per-string direction in language maps (e.g. titles and descriptions) and you could recommend the use of the language tag for these.
I would thus tend to say:
Strings on the Web recommends the use of metadata to determine the <a>base
direction</a> of string values. When metadata is not present, applications SHOULD
use <a>first-strong detection</a>as a fallback. Language maps do not permit per-string
metadata: implementations MAY infer the base direction from the language tag (as
a better indicator than first-strong detection).
Note that the links are found in i18n-glossary (you can add to your xrefs to pick up automagically)
index.template.html
Outdated
| Strings on the Web [[?STRING-META]] suggests | ||
| both strong-first and language-based inferencing as means | ||
| to determine the base text direction. |
|
@aphillips I have addressed your feedback. However, there is one small issue: we are using these definitions inside normative assertions but these definitions are informative in i18-glossary (which makes sense since it is just a glossary). Should I change something in the respec config? Important note for spec editors: I have changed the respec config |
|
from today's TD call:
|
|
many thanks! |
fixes #1414
See https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/pull/1437.html#example-8 for an easier review
Preview | Diff