- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Oct 2017 00:32:54 +0000
- To: public-css-archive@w3.org
Wouldn't the definition of how to read the propdef table be considered normative text (because if it isn't, propdefs do not have any unambiguously normative meaning)? That seems to exclude the snapshot as a host for them. If we were to start a css-core or css-meta spec of sorts, would there be anything else to put in there? Maybe: * https://www.w3.org/TR/CSS21/intro.html#q2.0 * https://www.w3.org/TR/CSS21/about.html#conventions * https://www.w3.org/TR/CSS21/conform.html#text-css > Relatedly, we copy the conformance boilerplate in every single module. Much of it used to be in snapshot, but was moved out when the snapshot was made non-normative. We already have the "Requirements for Responsible Implementation of CSS" subsection of the "Conformance" section. I agree with having the whole thing in there. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1867#issuecomment-336753668 using your GitHub account
Received on Monday, 16 October 2017 00:32:49 UTC