- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2023 09:01:42 +0000
- To: public-secondscreen@w3.org
These terms were locally re-defined because ReSpec did not have good support for cross-referencing sections in other specs that need to be interpreted as actual terms. ReSpec now has better support for that. Two options: 1. Keep a local definition. ```html <p>The term <dfn data-cite="rfc9110#rfc.section.12.5.4">Accept-Language</dfn> is used as defined in EcmaScript. [[!ECMASCRIPT]].</p> <p>I can then reference the term directly with <a>Accept-Language</a>.</p> ``` 2. Only use references: ```html <p>The term can be referenced directly through <a data-cite="rfc9110#rfc.section.12.5.4">Accept-Language</a>.</p> <p>But all occurrences need to have the same data-cite attribute, as in <a data-cite="rfc9110#rfc.section.12.5.4">Accept-Language</a>. <a>Accept-Language</a> won't work in particular.</p> ``` Both options will correctly put the term in the list of terms defined by reference. I personally prefer the second option that avoids creating an otherwise useless local definition, but it requires using the `data-cite` attribute in all references to the term. The same approach would work with most of the remaining terms in the Terminology section. Do you want me to update this pull request to apply the second option and extend it to other terms as well? -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/pull/518#issuecomment-1754765501 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 October 2023 09:01:43 UTC