- From: himorin / Atsushi Shimono via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Mar 2023 15:37:42 +0000
- To: public-i18n-archive@w3.org
@aphillips how about this?? ---- [Section 6. Links](https://www.w3.org/TR/2023/WD-wot-profile-20230118/#common-constraints-links) is not clear and unorganized on several points: 1. Link relation type is strongly connected with media types as constraints, but these mime types have additional constraints to these, which results in scattered descriptions and writings of specification. 2. Constraint for `service-doc` link relation type is written as > human readable documentation, supported formats are Unicode Text, markdown, HTML and PDF. but wording `Unicode` is not clear. Considering restrictions placed at mime types, it should be clearly stated with UTF-8 is mandatory over all applicable types. 3. hreflang is marked as optional, but should be mandatory for `text/plain`, `text/markdown`, and possibly on `text/html`. We would propose to rewrite this section into one table for clarification and ease for noticing all of constraints with reorganizing all of attached text for description totally, something like: | Relation-Type | Supported Media Types | Constraints | Remarks | |---|---|---|---| | `icon` | `image/png`, `image/jpeg` | | | | `service-doc` | `text/plain`, `text/html`, `text/markdown`, `text/pdf` | Linked files MUST use the UTF-8 character encoding. `hreflnag` is mandatory for `text/plain` and `text/markdown` | Human readable documentation. | -- GitHub Notification of comment by himorin Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1664#issuecomment-1476465022 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 March 2023 15:37:43 UTC