HTTP/2 200
date: Fri, 10 Oct 2025 01:59:25 GMT
content-type: text/html; charset=utf-8
content-encoding: gzip
content-location: 8b444a48b11b.html
vary: negotiate,Accept-Encoding
tcn: choice
strict-transport-security: max-age=63072000
content-security-policy: upgrade-insecure-requests;
last-modified: Mon, 01 Apr 2019 09:34:16 GMT
cache-control: public, max-age=2592000, s-maxage=2592000
cf-cache-status: HIT
set-cookie: __cf_bm=ArYt4t9t_wq7LXHlvdElscpiH_WwmMbYP5CDsWC6YoM-1760061565-1.0.1.1-wztabrKNbX4YMnbKadWQ3JUH3RM0b9XQZqUXr8.2pU1qrogBY5mLIm7BxENA1m3gDKahwKz9fJEvwx11_ce4iCjkuQ.ZdmTM43WREDICzc8; path=/; expires=Fri, 10-Oct-25 02:29:25 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c284a7ce6bf473-BLR
alt-svc: h3=":443"; ma=86400
Changed should to must for status info setting expectations about next steps. ISSUE-74
--- a/tr.html Wed Jan 22 12:53:23 2014 +0100
+++ b/tr.html Sun Feb 02 02:50:04 2014 +0100
@@ -92,11 +92,11 @@
transitions</li>
<li>If W3C closes a Working Group, they <em class="rfc2119">must</em>
republish its unfinished work as Notes. </li>
- <li>Implementation requirements for passing beyond Candidate Recommendation
- are not simply listed as "2 interoperable implementations", instead
- a new sections gives guidance on what is considered when assessing "<a
- href="#implementation-experience">adequate implementation
- experience</a>".</li>
+ <li>Implementation requirements for passing beyond Candidate
+ Recommendation are not simply listed as "2 interoperable
+ implementations", instead a new sections gives guidance on what is
+ considered when assessing "<a href="#implementation-experience">adequate
+ implementation experience</a>".</li>
<li>Instead of relying on a Last Call publication for adequate review
there is a requirement for a Working Group to demonstrate "<a href="#wide-review">wide
review</a>", while leaving them to achieve this as they see fit.</li>
@@ -378,10 +378,9 @@
<li><em class="rfc2119">must</em> state who developed the specification, </li>
<li><em class="rfc2119">must</em> state how to send comments or file bugs,
and where these are recorded, </li>
- <li> <em class="rfc2119">should</em> explain how the technology relates
- to existing international standards and related work inside or outside
- W3C,</li>
- <li><em class="rfc2119">should</em> include expectations about next steps,
+ <li><em class="rfc2119">must</em> include expectations about next steps,</li>
+ <li><em class="rfc2119">should</em> explain how the technology relates to
+ existing international standards and related work inside or outside W3C,
and</li>
<li><em class="rfc2119">should</em> explain or link to an explanation of
significant changes from the previous version.</li>