#tantekjust confirmed btw that the CSS WG does write tests for SHOULDs in their specs, but then document the test accordingly in itself, that it is testing a SHOULD
#tantekthis serves an important purpose, which is to gather implementer experience on SHOULDs
#tantekif it turns out that implementations all (or nearly all) pass a test of a SHOULD, that makes a good case for making it a MUST in an iteration of the spec
#tantekso whoever it was that said that "SHOULDS must not be tested" is empirically wrong
#tanteknot only are SHOULDs tested, but the data from such tests is useful and helps improve specs
#tantek(this is following up from a discussion in the afternoon of day 2 at our recent f2f at TPAC)
#tantekof course the better option is to eliminate as many SHOULDs as you can from your specs
#tantekif the reason for a SHOULD is "some implementations may not want / need to" then create an implementation profile / conformance class accordingly that either includes those requirements as MUST or not
#tantekleaving anything as a SHOULD provides insufficient guidance to implementers and is thus is a likely source of interop failure
#tantekand if it really is OPTIONAL then make it a MAY
shepazu, tantek, timbl, Karli and Karli_ joined the channel