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

modularity in specifications

From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
Date: Mon, 18 Mar 2002 09:55:10 -0500
Message-Id: <5.0.0.25.2.20020318093503.00ac8af0@mailserver.nist.gov>
To: www-qa-wg@w3.org
Hello all

I could use some guidance in writing the Specification Guideline.  In 
particular, can you tell me if the following makes sense for W3C 
specifications and if so, can you provide an example(s).  THANKS

1.  An implementation is composed of several components.  In order for the 
implementation to conform to the specification, all its components (the 
implementation's components) must also conform to the specification.  So,
-- Conformance of the implementation is the same as the sum of all its 
components, where each component conforms to the specification.  (Does this 
make sense for W3C specs?)  If what it means for a component to conform 
(e.g., claim conformance) is described, would conformance of the 
implementation also be specified?

2.  An implementation is composed of several components, where these 
components conform to another specification.   So, if this can happen, 
should we have a checkpoint that says that lists the specifications that 
the components conform to?

3.  A specification is dependent on other specifications.  As part of the 
conformance statements, should a checkpoint require that these other 
specifications and their affect on claiming conformance of this 
specification be described.  (Again does this make sense in W3C specs?)

4.  Any other cases of modularity and relationship between the modules that 
make up a spec?

Thanks for the assistance.
lynne

  
Received on Monday, 18 March 2002 09:51:12 GMT

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