A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "Problem Solving"

From WHATWG Wiki
Jump to: navigation, search
(Moved the current usage section as a new subsection of Problem Description.)
(Problem Description)
Line 4: Line 4:
  
 
== Problem Description ==
 
== Problem Description ==
:''Complete description of the problem, explanation of why the current markup is insufficient, etc.''
+
''Complete description of the problem.''
 +
 
 +
=== Current Limitations ===
 +
''Explanation of why the current markup is insufficient.''
  
 
=== Current Usage and Workarounds ===
 
=== Current Usage and Workarounds ===
:''Some evidence that this feature is desparately needed on the web.''
+
''Some evidence that this feature is desperately needed on the web.  You may provide a separate examples page for listing these.''
 +
 
 +
=== Benefits ===
 +
 
 +
''Explanation of how and why new markup would be useful.''
  
 
== Proposed Solutions ==
 
== Proposed Solutions ==

Revision as of 06:21, 17 November 2006

This is an empty page that describes what should be documented about a problem and the different solutions proposed to address it. Feel free to copy this template to when creating a new page.

Brief description of the problem to solve.

Problem Description

Complete description of the problem.

Current Limitations

Explanation of why the current markup is insufficient.

Current Usage and Workarounds

Some evidence that this feature is desperately needed on the web. You may provide a separate examples page for listing these.

Benefits

Explanation of how and why new markup would be useful.

Proposed Solutions

My Solution

Brief description of the solution and of how it address the problem at hand.

Processing Model

Explanation of the changes introduced by this solution. It explains how the document is processed, and how errors are handled. This should be very clear, including things such as event timing if the solution involves events, how to create graphs representing the data in the case of semantic proposals, etc.

Limitations

Cases not covered by this solution in relation to the problem description; other problems with this solution, if any.

Implementation

Description of how and why browser vendors would take advantage of this feature.

Adoption

Reasons why page authors would use this solution.