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 Chat (such as one of these permanent autoconfirmed members).
Talk:Problem Solving: Difference between revisions
Jump to navigation
Jump to search
Lachlan Hunt (talk | contribs) |
m (Typo Fix) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
* I just added a new page based on this template -- [[Link Hashes]] -- and I begin to wonder if the template should not be a lot more flexible regarding how the information is organised. There is just too much repetition of the same thing between different solutions, but if you compare to another problem -- like [[Image Caption]] -- repetitions are not on the same items. Maybe we should try to better organise these two problem pages and then update the template with what we've determined to be a good and flexible enough organisation. --[[User:Michel Fortin|Michel Fortin]] 09:52, 17 November 2006 (PST) | |||
== Problem Description == | == Problem Description == | ||
| Line 4: | Line 6: | ||
* 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 <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 <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. | ** 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. --[[User:Lachlan Hunt|Lachlan Hunt]] 09:37, 17 November 2006 (PST) | ||
Latest revision as of 17:58, 17 November 2006
- I just added a new page based on this template -- Link Hashes -- and I begin to wonder if the template should not be a lot more flexible regarding how the information is organised. There is just too much repetition of the same thing between different solutions, but if you compare to another problem -- like Image Caption -- repetitions are not on the same items. Maybe we should try to better organise these two problem pages and then update the template with what we've determined to be a good and flexible enough organisation. --Michel Fortin 09:52, 17 November 2006 (PST)
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. --Lachlan Hunt 09:37, 17 November 2006 (PST)