W3C home > Mailing lists > Public > www-qa-wg@w3.org > August 2002

Re: definition of strict conformance

From: David Marston/Cambridge/IBM <david_marston@us.ibm.com>
Date: Thu, 1 Aug 2002 16:20:42 -0400
To: www-qa-wg@w3.org
Message-ID: <OF464BF4E4.F1E7320C-ON85256C08.0068F930@lotus.com>

>>> is Lofton, earlier; >> is me, earlier; > is Lofton, last time

>So for example, in SVG Tiny, an implementation can choose whether to
>support embedded ECMAscript (within <script> tags), or not. And this
>disqualifies Tiny as a "strict conformance" definition?
>That seems fine to me.

Yes, that's what I meant. Glad you agree.

>>>Can there be "implementation dependent" features or behaviors?

>>If they fall under the guidelines for discretionary behaviors, which
>>would be broader than discretionary *choices*, then yes.

>This one I have more trouble with.  Perhaps because I consider
>"implementation dependent" to be the Ultimate Evil for interoperability.

A good example is choice of encodings. "Strict conformance" means that
the implementation must support, say, UTF-8 and UTF-16 but nothing else.
If they have the discretion to also support other encodings, then a
test suite can at least use UTF-8 with confidence. If the choice of
encodings is fully "implementation-dependent", then you can't count on
any particular encoding, so how do you write a test suite?

My hope is that we can combine discretionary CHOICES with discretionary
behavior (a.k.a. "implementation-dependent") for SpecGL at least, to
avoid having two separate Dimensions of Variability that are very
similar. Maybe the Glossary will need some adjustment.
.................David Marston
Received on Thursday, 1 August 2002 16:21:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:28 UTC