include-pattern-issues: Difference between revisions
Jump to navigation
Jump to search
m (a few details) |
|||
| Line 4: | Line 4: | ||
* {{OpenIssue}} 2007-08-03D raised by [http://www.kaply.com/weblog/ Mike Kaply]. | * {{OpenIssue}} 2007-08-03D raised by [http://www.kaply.com/weblog/ Mike Kaply]. | ||
*# ''Issue 1: It needs to be explicit that the only classname on the object/etc should be include. Having classnames on the object is not necessary since the premise is that the object node is REPLACED by the referenced node.'' | *# ''Issue 1: It needs to be explicit that the only classname on the object/etc should be include. Having specific microformat property classnames (e.g. "fn") on the object is not necessary since the premise is that the object node is REPLACED by the referenced node.'' | ||
Revision as of 20:38, 3 August 2007
Include-Pattern Issues
See: A summary of issues with the include pattern.
- open issue! 2007-08-03D raised by Mike Kaply.
- Issue 1: It needs to be explicit that the only classname on the object/etc should be include. Having specific microformat property classnames (e.g. "fn") on the object is not necessary since the premise is that the object node is REPLACED by the referenced node.
Related Pages
- the include pattern
- include-pattern examples in the wild - an on-going list of websites which use the include pattern.
- include-pattern FAQ - if you have any questions about the include pattern, check here, and if you don't find answers, add your questions!
- include-pattern feedback- general feedback (as opposed to specific issues).
- include-pattern issues - specific issues with the include pattern.
- include-pattern strawman - alternative proposals