include-pattern-issues

2008-12-19T13:24:01Z

RoldrOnc4t: montroczel

getc4ta
=Include-Pattern Issues=

See: [http://microformats.org/discuss/mail/microformats-dev/2006-May/000097.html A summary of issues with the include pattern].

<div class="vevent">
* {{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">
*# 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 class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-21</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span>
<div class="description">
It's very easy for inclusions to end up as an infinite loop. For example:
<pre><div class="fn" id="foo"><a class="include" href="#foo">include</a></div></pre>
Assuming that we want to allow multi-level inclusion (e.g. an hcard could include an "adr" from elsewhere on the page, which in turn might include a "locality" from somewhere else), loops are hard to avoid. In my own parser, I assume a maximum number of iterations over the inclusion function. This level is set higher for more complex microformats than the more simple ones -- for example an hCard is allowed up to six iterations, whereas a geo is only allowed up to two.
</div>
</div>

== Template ==

{{issues-format}}

==Related Pages==
{{include-pattern-related-pages}}

Microformats Wiki - User contributions [en]

include-pattern-issues