agenda+ Defining Conformance - addressing GH Issues We are going to start working on the Github issues related to definitions of conformance. Github Issues related to defining conformance: * 38 <https://github.com/w3c/silver/issues/38>- allow test coverage to be less than 100% * 304 <https://github.com/w3c/silver/issues/304> - conformance claims need feedback mechanisms * 352 <https://github.com/w3c/silver/issues/352>- multiple conformance models vs simplicity * 386 <https://github.com/w3c/silver/issues/386>- if we allow 95% to pass, people will stop at 95%. Proposal for addressing minor errors * 394 <https://github.com/w3c/silver/issues/394>- the effort of proving conformance can overshadow development. * 425 <https://github.com/w3c/silver/issues/425>- will it be possible for multiple means of measurement to determine if the website conforms? * 448 <https://github.com/w3c/silver/issues/448>- a small minority of pages with "critical errors" should still pass. Important to large and dynamic sites. * 457 <https://github.com/w3c/silver/issues/457>- wants flexible conformance for 3rd party, but doesn't want multiple conformance models * 460 <https://github.com/w3c/silver/issues/460>- flexibility for conformance is desperately needed. Incentive for adoption. * 470 <https://github.com/w3c/silver/issues/470>- process approach allows orgs to focus on making core tasks accessible. More clarity on defining process. * 494 <https://github.com/w3c/silver/issues/494>- how will content-free applications like CMS be evaluated and scored? == Conference Call Info == https://www.w3.org/2017/08/telecon-info_silver-friReceived on Friday, 12 November 2021 01:16:59 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:54 UTC