<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>1041</bug_id>
          
          <creation_ts>2005-01-21 09:37:05 +0000</creation_ts>
          <short_desc>Conformance is not a yes/no proposition (wrt filling an ICS)</short_desc>
          <delta_ts>2005-04-28 11:53:52 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>QA</product>
          <component>QASpec-GL</component>
          <version>LC-2004-11-22</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>REMIND</resolution>
          
          
          <bug_file_loc>http://lists.w3.org/Archives/Public/www-qa/2005Jan/0006.html</bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>1157</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Dominique Hazael-Massieux">dom</reporter>
          <assigned_to name="Karl Dubost">karl</assigned_to>
          
          
          <qa_contact name="Karl Dubost">karl</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>2861</commentid>
    <comment_count>0</comment_count>
    <who name="Dominique Hazael-Massieux">dom</who>
    <bug_when>2005-01-21 09:37:05 +0000</bug_when>
    <thetext>&quot;1.2 Good Practice B&quot; suggests that an ICS form be provided with
yes/no questions: &quot;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&quot;.
However, this is unrealistic. For example, take CSS user agents. How
is an implementor to determine if he has implemented margin collapsing
correctly? All that can really be said is that the user agent passes a
certain set of tests. For any even mildly complicated specification it
will always be possible to show that a user agent is in some way
non-compliant, it&apos;s just a matter of finding a suitable test.

Therefore I would suggest changing this section to instead suggest
leaving space for the implementor to list the URIs to (publically
available) tests that the implementor has used to verify
interoperability and compliance, listing which tests the implementor
determined passed in the user agent and which failed (if any).
Specification authors may wish to provide a list of URIs to the tests
that form part of the specification&apos;s formal test suite (as used to
check for interoperability as per the CR exit criteria), although
naturally such a test suite can never be complete enough to really be
used to claim conformance so implementors would be expected to also
provide links to other tests that they used.

(The existing suggestions could be kept for the rare specs in which a
test suite is inappropriate, such as the two examples the spec
currently gives: the QA spec guidelines and the WCAG. However, this
applies to very few specifications and so should not IMHO be the
primary suggestion in the document.)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>4100</commentid>
    <comment_count>1</comment_count>
    <who name="Karl Dubost">karl</who>
    <bug_when>2005-03-03 17:33:17 +0000</bug_when>
    <thetext>http://lists.w3.org/Archives/Public/www-qa-wg/2005Feb/0021.html

(dh) What I understand from Ian&apos;s email is that you cannot ever say  
that you are fully conformant to a spec; it&apos;s not a yes/no proposition.
(pc) Conformance is not binary. While it&apos;s not possible to claim with  
100% certainty that an implementation is conformant to every aspect of  
a specification, but rather as to whether the conformance _REQUIREMENT_  
has been met (for example, passing these tests etc). It&apos;s up to the  
spec writers to make it &quot;binary&quot; or easy to answer. We use the term  
conformanace in a special sense. If we require conformance in this  
sense, we need to rewrite specifications to meet this need.
(lr) To me, a conformance statement is a vendor declaration that they  
implement this or that feature.
(kd) [minuter: sound breaking up]... maybe we can add a clause to Spec  
GL ...
(dm) the ICS is also an input to the processor running the test
(lr) I&apos;d say selecting the tests that are run. I&apos;ll take a stab at  
review and modify wording as necessary, by feb 11.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>4113</commentid>
    <comment_count>2</comment_count>
    <who name="Karl Dubost">karl</who>
    <bug_when>2005-03-03 19:22:18 +0000</bug_when>
    <thetext>http://lists.w3.org/Archives/Public/www-qa-wg/2005Feb/0028.html
       http://www.w3.org/Bugs/Public/show_bug.cgi?id=1041
       Ongoing: LH will modify the wording. Due date is February 21.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>4114</commentid>
    <comment_count>3</comment_count>
    <who name="Karl Dubost">karl</who>
    <bug_when>2005-03-03 19:24:05 +0000</bug_when>
    <thetext>http://lists.w3.org/Archives/Public/www-qa-wg/2005Feb/0014.html

Action Item  to modify 1.2 B GP ICS
I tweaked the what does it mean, removing &apos;conformance&apos; from the first 
sentence, changing some works and adding a new last sentence.

What does it mean?
An Implementation Conformance Statement (ICS) provides information about an 
implementation to a specification, by presenting in a uniform manner the 
capabilities and optional features that have been implemented as well as 
the limitations of the implementation..   An ICS typically takes the form 
of a questionnaire or checklist for implementor to complete.  An ICS 
provides the implementor a way to indicate what has been implemented.
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>3885</commentid>
    <comment_count>4</comment_count>
    <who name="Dominique Hazael-Massieux">dom</who>
    <bug_when>2005-03-08 14:26:42 +0000</bug_when>
    <thetext>Lynne has an action item to provide clarification wrt real meaning of ICS:
AI-20050303-1 LR to provide a 1 sentence disclaimer in the&quot;What does it mean&quot;
section that the ICS should positively emphasize that it&apos;s not about conformance.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>3836</commentid>
    <comment_count>5</comment_count>
    <who name="Dominique Hazael-Massieux">dom</who>
    <bug_when>2005-04-08 09:29:01 +0000</bug_when>
    <thetext>Lynne&apos;s proposal integrated as amended by later proposal.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>3688</commentid>
    <comment_count>6</comment_count>
    <who name="Dominique Hazael-Massieux">dom</who>
    <bug_when>2005-04-28 11:53:52 +0000</bug_when>
    <thetext>setting version to LC in case of future use</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>