W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2009

Re: marking up normative requrements (was: Re: Testing framework requirements)

From: Simon Pieters <simonp@opera.com>
Date: Mon, 20 Jul 2009 13:03:29 +0200
To: "Hallvord R. M. Steen" <hallvord@opera.com>, "Doug Schepers" <schepers@w3.org>
Cc: "Garrett Smith" <dhtmlkitchen@gmail.com>, "Travis Leithead" <travil@microsoft.com>, "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <op.uxc4z3f0idj3kv@simon-pieterss-macbook.local>
On Mon, 20 Jul 2009 12:36:26 +0200, Hallvord R. M. Steen  
<hallvord@opera.com> wrote:

> On Mon, 20 Jul 2009 08:54:36 +0200, Doug Schepers <schepers@w3.org>  
> wrote:
>
>> We might need to come up with some convention for marking up the  
>> normative requirements in the spec itself to facilitate this
>
> This is a very simple and good idea - we should start doing this ASAP.  
> Would a simple <span class="req"> do? A trivial bit of JS or other  
> processing could add IDs before final publishing (<span class="req"  
> id="req1">), and tests refer back to spec.html#req1 etc..

There is already a convention -- the use of RFC2119 keywords.

http://philip.html5.org/tests/canvas/suite-20080624/tests/ has an  
annotated version of the HTML 5 spec, with references from the test cases.

-- 
Simon Pieters
Opera Software
Received on Monday, 20 July 2009 11:04:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:03 GMT