Difference between revisions of "include-pattern-issues"

From Microformats Wiki
Jump to navigation Jump to search
m ({{issues-format}})
(→‎Include-Pattern Issues: Marking Mike Kapley's issue closed)
Line 4: Line 4:
  
 
<div class="vevent">
 
<div class="vevent">
* {{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>
+
* {{ClosedIssue}} <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">
 
<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.
+
*# 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. This is clarified on February 12th 2008, line 27 (http://microformats.org/wiki?title=include-pattern&diff=0&oldid=25677)
 
</div>
 
</div>
 
</div>
 
</div>

Revision as of 03:02, 12 February 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. This is clarified on February 12th 2008, line 27 (http://microformats.org/wiki?title=include-pattern&diff=0&oldid=25677)

Template

Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>

Related Pages