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

Re: [SpecGL Draft] A.2 Provide an Implementation Conformance Statement (ICS) proforma.

From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
Date: Fri, 13 Aug 2004 18:07:51 -0400
Message-Id: <5.1.0.14.2.20040813173351.00b11848@mailserver.nist.gov>
To: www-qa-wg@w3.org


>>
>>
>>Good Practice:
>>         Provide an Implementation Conformance Statement (ICS) proforma.
>>
>>What does it mean?
>>         An Implementation Conformance Statement (ICS) provides 
>> standardized information about the conformance of an implementation to 
>> the specification. It indicates which capabilities and options have been 
>> implemented, as well as the limitations of the implementation. An ICS 
>> typically takes the form of a questionnaire or a checklist for 
>> implementor to complete. This Good Practice suggests that the 
>> specification itself include an ICS proforma. (Caveat. The ICS concept 
>> may be inapplicable to some types of specifications.)

s/It indicates which/It is used to indicate which/


>>Why care?
>>         An ICS provides detail about conformance. The detail can, for 
>> example, be used to identify the subset of a conformance test suite that 
>> is applicable to the implementation to be tested. An ICS can also be 
>> especially valuable in optionality choices in the implementation, and 
>> documenting the presence of extensions.
>>         The ICS is also a good tool to help implementors claim 
>> conformance to the technology and use the specific wording, that has 
>> been defined for this purpose.

Rewrite suggestion:
An ICS provides detail about conformance. View the ICS as a template, where 
its organization, format and content can provide implementers and users a 
quick overview of the specification's features, options, subdivisions of 
the technology, conformance requirements, etc. It can be especially 
valuable as a statement of conformance, where implementers indicate which 
mandatory features and options they implement and document the presence of 
extensions.  Once completed by an implementer it can be used as part of the 
conformance claim.  Additionally, an ICS can be used to identify the subset 
of a conformance test suite that would be applicable to the implementation 
to be tested.

>>Related:
>>         Conformance claim wording
>>         Test Assertions.
>>
>>Technique:
>>1. List your test assertions
>>2. Organize your test assertions following the subdivisions of the 
>>specification if there are.
>>3. If there are dependencies, express them. (For instance, if No to this 
>>question, jump to the next section.)
>>4. Define a list, a table or  a form that will give the possibility to 
>>the implementers to check: Yes, No, Not Applicable
>>5. You may want give a tool that will help the implementors to fill the 
>>ICS and have a formatted report  (for example, with EARL).

Suggest changing test assertions to features or capabilities -
Suggest:
1.  Create a list, table or form listing all features (capabilities) and 
indicating if it is mandatory or not.
2. Provide space for the implementer to check: Yes, No, Not Applicable
3.  Organize the features according to the subdivisions of the 
specification or in the order they occur in the specification or in some 
other logical grouping
4. (your #3)
5. (your #5)  You may want to provide a tool....to complete the ICS ...


>>Examples
>>
>>WCAG 1.0


--Lynne
Received on Friday, 13 August 2004 22:08:13 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:17 GMT