Difference between revisions of "include-pattern-issues"

From Microformats Wiki
Jump to navigation Jump to search
m (a few details)
m (fmt)
Line 3: Line 3:
 
See: [http://microformats.org/discuss/mail/microformats-dev/2006-May/000097.html A summary of issues with the include pattern].
 
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==
 
==Related Pages==
 
{{include-pattern-related-pages}}
 
{{include-pattern-related-pages}}

Revision as of 11:08, 14 January 2008

Include-Pattern Issues

See: A summary of issues with the include pattern.

    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