- From: himorin / Atsushi Shimono via GitHub <noreply@w3.org>
- Date: Thu, 07 May 2026 20:28:49 +0000
- To: public-device-apis-log@w3.org
@reillyeon some level of guidance to store resources under w3.org are placed for /TR/ publication, like required files for rendering (images, styles, etc.) are required to be under w3.org and will be [rejected by pubrules](https://github.com/w3c/specberus/blob/dd3b1980f7b3adc7ccebd2ae59ba53669db4931f/lib/rules.json#L1454) during processing. I personally don't have clear knowledge on implementation report, on either requirement at w3.org or secured snapshot, such that wpt.fyi will be changed dynamically and cannot be considered snapshot at specific time if sha parameter or something is not included like [css-box-3](https://www.w3.org/TR/2024/REC-css-box-3-20240411/), or many RECs uses github.io (e.g. [WebRTC](https://www.w3.org/TR/2025/REC-webrtc-20250313/)) or drafts.csswg.org (e.g. [mediaqueries-3](https://www.w3.org/TR/2024/REC-mediaqueries-3-20240521/)). But, I **personally** consider it might be better to store final content under w3.org, and proposed two options. Although there are [small number of examples that implementation report published as NOTE](https://www.w3.org/TR/?filter-tr-name=implementation+report), I suppose having report under the published spec could be easier and simpler... (but no strong opinion here) any additional point to be considered? > @tidoust -- GitHub Notification of comment by himorin Please view or discuss this issue at https://github.com/w3c/vibration/issues/62#issuecomment-4400820859 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 May 2026 20:28:54 UTC