RE: css3-fonts: should not dictate usage policy with respect to origin
Sylvain Galineau <[email protected]> Tue, 28 Jun 2011 01:32:35 +0000
| Newsgroups | gmane.comp.web.fonts,gmane.comp.web.css.general |
|---|---|
| Message-ID | <3C4041FF83E1E04A986B6DC50F0178290B92FD@TK5EX14MBXC297.redmond.corp.microsoft.com> |
It is the CSSWG’s process and css3-fonts is in the CSSWG charter. Certification has not relevance here. Can we stick to the topic at hand or are we now embarking on discussing new made-up issues ? From: Glenn Adams [mailto:[email protected]] Sent: Monday, June 27, 2011 5:51 PM To: Sylvain Galineau Cc: Levantovsky, Vladimir; [email protected]; StyleBeyondthePunchedCard; [email protected]; [email protected]; Martin J. Subject: Re: css3-fonts: should not dictate usage policy with respect to origin That may be the case, but it is outside of nominal W3C processes, and is not understood by members to be part of the process of going to REC. Further, it certainly does not constitute a compliance testing or certification process. G. On Mon, Jun 27, 2011 at 6:45 PM, Sylvain Galineau <[email protected]<mailto:[email protected]>> wrote: The CSS WG has agreed that in order to drop their vendor prefix implementors will have to publish an IR - and, if need be, the testcases used for this IR - to demonstrate how and why they believe their unprefixed version to be conformant with the spec. From: Glenn Adams [mailto:[email protected]<mailto:[email protected]>] Sent: Monday, June 27, 2011 5:07 PM To: Sylvain Galineau Cc: Levantovsky, Vladimir; [email protected]<mailto:[email protected]>; StyleBeyondthePunchedCard; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Martin J. Subject: Re: css3-fonts: should not dictate usage policy with respect to origin On Mon, Jun 27, 2011 at 5:33 PM, Sylvain Galineau <[email protected]<mailto:[email protected]>> wrote: UA vendors demonstrate conformance with a CSS module by publishing an implementation report (IR) based on a test suite reviewed and approved by the WG. That may be the case, but it is not the purpose of the IR or the test suite. The purpose of W3C IRs and test suites is to demonstrate two or more implementations of each defined feature. This is a defined part of the W3C process with the express goal of demonstrating the implementability of defined features. Testing or verifying compliance of an implementation with a W3C spec is NOT the purpose of the IR or a W3C test suite. Notwithstanding this fact, such a test suite may be a useful tool in such a process, but it is not the purpose of the IR or test suite. The W3C does not publish compliance requirements on real world implementations nor does it define a process by means of which an implementation may be certified to be compliant (with conformance requirements). G.