W3C home > Mailing lists > Public > www-qa@w3.org > January 2005

QA Framework: Specification Guidelines: Parsing the definition of specification

From: Gary Feldman <g1list_1a@marsdome.com>
Date: Wed, 26 Jan 2005 09:35:29 -0500
Message-ID: <41F7AAB1.50103@marsdome.com>
To: www-qa@w3.org

I found it difficult to parse and understand the definition of 
specification.  It says "...interface to accomplish a task."  But 
interfaces are static, passive entities.  They don't accomplish 
anything.  Perhaps "for accomplishing a task" would read better, but 
even that feels uncomfortable.  What task does XML accomplish?  (It is 
used for many more things besides machine-independent data interchange.)

I'm not sure that this phrase is necessary at all.  Saying that "A 
specification is a set of technical requirements which define a reliable 
interface." seems adequate.  If really necessary to qualify "interface", 
then "interface between actors" is what I'd suggest.

On the same sentence, though less important, the phrase "which aim at 
..." is one of those unnecessary phrases (like "in order to") that are 
best removed.

Received on Wednesday, 26 January 2005 14:35:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:40:36 UTC