W3C home > Mailing lists > Public > www-qa-wg@w3.org > July 2003

Fwd: Cc/pp S&V conformance section

From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
Date: Mon, 07 Jul 2003 10:30:44 -0400
Message-Id: <5.1.0.14.2.20030707103012.01c64368@mailserver.nist.gov>
To: www-qa-wg@w3.org
We were asked to comment on the CC/PP conformance section, explicitly the 
section on cnsumer conformance. Here is my proposed text.  If anyone has 
any comments, additions, edits on my text (below) or the CC/PP, please send 
it to me so I can consolidate and send it.  Deadline is July 13.

Thanks Lynne
+++++++++++++++++++++++++++++++++++++++++++++++++
My proposed comments:

Thank you for the opportunity to comment on your conformance section and 
CC/PP document.

Adding the classes of products for CC/PP helped to focus the 
requirements.  Developers in my organization found it helpful in allowing 
them to concentrate on the relevant areas of the specification and helped 
ensure that they didn't miss a requirement.

Comments on 5.4 CC/PP Consumer Conformance.

 >We defined a test suite in which we defined a set of features to test on
 >different consumer implementations to check the interoperability.
 >For each test, we are providing valid and invalid profiles to illustrate
 >it. However, we are not sure at all that an implementation passing all 
these tests
 >could be considered conformant to the spec and say so.  Indeed that just a
 >small set of tests to test interoperability and not to make an
 >extensive check of implementation capabilities and conformance. So we
 >have quite trouble defining the conformance criteria for the consumer.

Conformance tests are never exhaustive, so you can never test 
everything.  It is especially difficult to define tests for 
consumers.  That is why the Specification Guidelines checkpoint 11.3, 
requires a conformance disclaimer.

A difficult section to write, since the statements are somewhat circular, 
that is, they depend on one another.  The key is to describe what is 
required for a conformant consumer.  Keep in mind that it isn't always easy 
or possible to test for conformance, but that it should be clear to the 
developer what the implementation must be able to do.

1. What is meant by 'extracts appropriate information'.  Since 
'appropriate' is vague and subjective, can this be made more specific?

2. It may be clearer to be more explicit regarding a consumer's support (or 
non support) for Appendix B.  If I understand correctly, support for the 
RDF Schema is mandatory for validating consumers.

3. Editorial:  Change 'all' to 'any' in non-validating: A consumer is a 
CC/PP conformant non-validating consumer when it does not reject all 
non-conformant CC/PP documents.


4. Comments on 5.5.2 Well-formed.
Add to the list of information to be included in a claim, the name 
(identify) of the implementation to which the claim is being made. Also, a 
version, date, or other identifier should be included to uniquely identify 
the implementation.
***************************************************8


>X-Sieve: CMU Sieve 2.2
>Resent-Date: Fri, 27 Jun 2003 09:29:38 -0400 (EDT)
>From: "boyera stephane" <boyera@w3.org>
>To: <lynne.rosenthal@nist.gov>, <www-qa-wg@w3.org>
>Cc: "'W3C DIWG'" <w3c-di-wg@w3.org>
>Date: Fri, 27 Jun 2003 15:29:33 +0200
>Organization: w3c
>X-Mailer: Microsoft Outlook, Build 10.0.2627
>Importance: Normal
>Subject: Cc/pp S&V conformance section
>X-Archived-At: http://www.w3.org/mid/004401c33cb0$25b18f10$06ca608a@inria.fr
>Resent-From: www-qa-wg@w3.org
>X-Mailing-List: <www-qa-wg@w3.org> archive/latest/2139
>X-Loop: www-qa-wg@w3.org
>Sender: www-qa-wg-request@w3.org
>Resent-Sender: www-qa-wg-request@w3.org
>List-Id: <www-qa-wg.w3.org>
>List-Help: <http://www.w3.org/Mail/>
>List-Unsubscribe: <mailto:www-qa-wg-request@w3.org?subject=unsubscribe>
>
>Dear Lynne and QAWG,
>
>
>I'm sending you this mail on the behald of DIWG, following the comments
>you sent us wrt the LCWD of CC/PP Structure and Vocabularies.
>
>We eventually drafted a conformance section for the spec, i'm attaching
>it to this mail.
>Please review and comment it.
>
>However, we still have few questions we were not able to answer in the
>group: particularly we have problem with the definition of section 5.4
>of what is a conformant consumer:
>We defined a test suite in which we defined a set of features to test on
>different consumer implementations to check the interoperability.
>Foreach test, we are providing valid and invalid profiles to illustrate
>it.
>However, we are not sure at all that an implementation passing all these
>tests could be considered conformant to the spec and say so. Indeed that
>just a small set of tests to test interoperability and not to make an
>extensive check of implementation capabilities and conformance. So we
>have quite trouble defining the conformance criteria for the consumer.
>So we are waiting for advices on this point.
>
>Thanks a lot in advance for any help
>Stephane
>
>
>--
>Stephane Boyera         stephane@w3.org
>W3C                             +33 (0) 4 92 38 78 34
>BP 93                           fax: +33 (0) 4 92 38 78 22
>F-06902 Sophia Antipolis Cedex,
>France
>


Received on Monday, 7 July 2003 10:31:05 GMT

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