- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Aug 2020 17:15:45 +0000
- To: public-css-archive@w3.org
browser-specs uses the shortname of the spec published under https://www.w3.org/TR/ by default (when the spec has been published there). In this case, browser-specs has one `CSS21` entry and one `CSS22` entry. The default rule that we have followed for series shortname is to drop all version numbers, hence `CSS`. I don't know if that's fantastic but at least that's consistent with the way other series are being treated. The series shortname is actually managed by the [W3C API](https://api.w3.org/doc), which browser-specs uses as source of knowledge for W3C specs. From a W3C API perspective, `CSS2` is merely an alias to (currently) `CSS21`. browser-specs does not have a notion of aliases. What may make this case clumsy is that CSS Snapshot specs, with shortnames such as `CSS-2015`, also end up being part of the same `CSS` series. These specs are not in browser-specs though, so I don't know if that really is a problem. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5442#issuecomment-675606080 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 August 2020 17:15:47 UTC