Re: definition of strict conformance

"Where all products of a class must be exactly alike, it should be clear
that a "strict conformance" policy is in effect for that product class.
Strict conformance is defined as conformance of an implementation that
employs only the requirements of the specification and no more (e.g., no
extensions)."

My answers to Lofton's questions:

>Are discretionary choices allowed?
Yes. I know, it mocks the word "strict", but I don't think a prohibition
is feasible when added to all the other prohibitions attending "strict".

>Are optional features allowed?
No, but you can have strict conformance on a per-module basis. This is
one of those fine points that I think should be saved for after the next
WD is published.

>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.
.................David Marston

Received on Thursday, 1 August 2002 11:06:50 UTC