anti-design-patterns: Difference between revisions
Jump to navigation
Jump to search
(drafted) |
mNo edit summary |
||
| Line 3: | Line 3: | ||
Just as there are [[design-patterns]] to encourage and follow, there are '''anti-design-patterns''' to discourage and avoid. | Just as there are [[design-patterns]] to encourage and follow, there are '''anti-design-patterns''' to discourage and avoid. | ||
== rel formatname == | |||
rel="formatname", e.g. rel="hcard" | |||
* | |||
Problems: | |||
* Indicating the ''type'' of the information does not indicate the ''semantic''. This was one of the mistakes in the design of XML-RPC and should not be propagated to rel values. | |||
* In particular such a rel value failes to capture and represent/indicate an explicit semantic, like "this over here is my hCard". See [[hcard-brainstorming#Auto-Discovery|hCard brainstorming on auto-discovery]] for current thoughts on this problem. | |||
== See Also == | == See Also == | ||
* [[design-patterns]] | * [[design-patterns]] | ||
Revision as of 15:42, 21 May 2007
anti-design-patterns
Just as there are design-patterns to encourage and follow, there are anti-design-patterns to discourage and avoid.
rel formatname
rel="formatname", e.g. rel="hcard"
Problems:
- Indicating the type of the information does not indicate the semantic. This was one of the mistakes in the design of XML-RPC and should not be propagated to rel values.
- In particular such a rel value failes to capture and represent/indicate an explicit semantic, like "this over here is my hCard". See hCard brainstorming on auto-discovery for current thoughts on this problem.