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 "Talk:Problem Solving"

From WHATWG Wiki
Jump to: navigation, search
m (Current Limitations)
(Current Limitations)
Line 3: Line 3:
 
=== Current Limitations ===
 
=== Current Limitations ===
  
I think "Current Limitations" and "Problem Description" will generally be the same thing. Almost always, the problem <em>is</em> a current limitation. Sure we could formulate problems in more general term, like "Problem: need to markup a dialogue; Limitation: no semantic markup for that", but in fact, marking up the dialog isn't really a problem (it's easy to markup a dialog with &lt;dl>), the limitation is. --[[User:Michel Fortin|Michel Fortin]] 07:17, 17 November 2006 (PST)
+
* I think "Current Limitations" and "Problem Description" will generally be the same thing. Almost always, the problem <em>is</em> a current limitation. Sure we could formulate problems in more general term, like "Problem: need to markup a dialogue; Limitation: no semantic markup for that", but in fact, marking up the dialog isn't really a problem (it's easy to markup a dialog with &lt;dl>), the limitation is. --[[User:Michel Fortin|Michel Fortin]] 07:17, 17 November 2006 (PST)
 +
** I changed Problem Description to Use Case Description to clarify why I think they're different.  The use case is about describing what kind of information you are trying to mark up.  The current limitations is for explaining why existing markup is not appropriate.

Revision as of 17:36, 17 November 2006

Problem Description

Current Limitations

  • I think "Current Limitations" and "Problem Description" will generally be the same thing. Almost always, the problem is a current limitation. Sure we could formulate problems in more general term, like "Problem: need to markup a dialogue; Limitation: no semantic markup for that", but in fact, marking up the dialog isn't really a problem (it's easy to markup a dialog with <dl>), the limitation is. --Michel Fortin 07:17, 17 November 2006 (PST)
    • I changed Problem Description to Use Case Description to clarify why I think they're different. The use case is about describing what kind of information you are trying to mark up. The current limitations is for explaining why existing markup is not appropriate.