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

RE: Testable assertion tagging for W3C specifications

From: Paul Cotton <pcotton@microsoft.com>
Date: Mon, 6 May 2002 22:37:55 -0400
Message-ID: <E7AC4500EAB7A442ABA7521D18814397032F94CE@tor-msg-01.northamerica.corp.microsoft.com>
To: "Jonathan Robie" <jonathan.robie@datadirect-technologies.com>, "Lofton Henderson" <lofton@rockynet.com>, <scott_boag@us.ibm.com>
Cc: <spec-prod@w3.org>, <w3c-query-editors@w3.org>, <www-qa@w3.org>
>I don't know the cost, and I don't know the benefit.

Another technique is to have a separate test/conformance document that
points directly into a technical specification or quotes test from the
normative document.  For example, see the SOAP 1.2 test/conformance
document [1].

[1] http://www.w3.org/2000/xp/Group/2/03/11/soap-1.2-conformance.html 

Paul Cotton, Microsoft Canada 
17 Eleanor Drive, Nepean, Ontario K2E 6A3 
Tel: (613) 225-5445 Fax: (425) 936-7329 

> -----Original Message-----
> From: Jonathan Robie
> Sent: Monday, May 06, 2002 6:03 PM
> To: Lofton Henderson; scott_boag@us.ibm.com
> Cc: spec-prod@w3.org; w3c-query-editors@w3.org; www-qa@w3.org
> Subject: Re: Testable assertion tagging for W3C specifications
> We already do some things to ensure consistency and correctness in our
> documents.
> We use xmlspec, which gives us consistency in markup and formatting
> conventions. We use conventions for our markup that allow us to do
> that extract the queries from the use cases or the XQuery spec, so
that we
> can run them through a parser or test them against an implementation
> does require some manual intervention). We generate a parser from the
> markup that generates the productions for the grammar in our
documents. We
> have a Formal Semantics document. All of these things result in real
> effort, but we have decided that the quality gains associated with
> justify the effort.
> Can someone do a mockup of how automatic tagging of assertions would
> used, the level of correctness that could be guaranteed from this
> approach,
> the extent to which this constrains editors in describing features,
> So
> far, I have not heard anything concrete enough to let me assess the
> cost/benefit. I don't know the cost, and I don't know the benefit.
> Jonathan
Received on Monday, 6 May 2002 22:38:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:43:19 UTC