

NEW ISSUE: 3989 [Guidelines] Suggested Format

From: Asir Vedamuthu <asirveda@microsoft.com>
Date: Fri, 17 Nov 2006 17:56:02 -0800
Message-ID: <1E0F0378382054439F14D5450650478F0B5447EE@RED-MSG-42.redmond.corp.microsoft.com>

Title: Suggested format for the Guidelines document.


Guidelines and best practices in the Guidelines document [1] are hidden
in the prose. They are not easy to pull out.

Assertion authors would find it very useful if the Guidelines document
identifies a scenario, articulates the problem statement at the
assertion design level, enumerates the factors to be considered and
highlights good practices.

The Architecture of the WWW document [2] is a good model to follow.
Furthermore, providing the assertion authors with a list of good
practice statements upfront (for instance [3]) would be very useful.


Guidelines and best practices are hidden in the prose. Assertion authors
need to read this document multiple times and dig for guidelines and
best practices. If the guidelines are clear and easy to find, the WG
(and other WGs such as I18N WG) will find it easy to review the
document, build consensus and adopt them.

Target: Guidelines for Assertion Authors.


We suggest using good practice statements as the center stage to
describe the guidelines for assertion authors. We request the WG to
consider the following possibilities:

a) Use a format similar to the Architecture of the WWW document
b) Provide a list of good practice statements upfront (after the Table
of Contents or in the Introduction).
c) Both a and b.

[2] http://www.w3.org/TR/webarch/ 
[3] http://www.w3.org/TR/webarch/#p10 

Asir S Vedamuthu
Microsoft Corporation
Received on Saturday, 18 November 2006 01:56:47 GMT
