Revision as of 11:08, 14 January 2008

Include-Pattern Issues

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.

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

@@ Line 3: / Line 3: @@
 See: [http://microformats.org/discuss/mail/microformats-dev/2006-May/000097.html A summary of issues with the include pattern].
-* {{OpenIssue}} 2007-08-03D raised by [http://www.kaply.com/weblog/ Mike Kaply].
+<div class="vevent">
-*# ''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.''
+* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2007-08-03</span> raised by <span class="fn">[http://www.kaply.com/weblog/ Mike Kaply]</span></span>
+<div class="description">
+*# 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.
+</div>
+</div>
 ==Related Pages==
 {{include-pattern-related-pages}}