> There are still issues of one include including another include which
> references the first include, but yes, preventing the inclusion of an
> ancestor node does go a long way to a solution.
Once one replaces an include element with the referenced subtree, then
any include in that subtree would be referencing an ancestor if it was
referencing the original include.
The following illustrates your case:
<span id="root">
<a class="include" href="#child"/>
</span>
<span id="child">
<a class="include" href="#root"/>
</span>
But once the include replacement is done, the tree looks like this:
<span id="root">
<span id="child">
<a class="include" href="#root"/>
</span>
</span>
<span id="child">
<span id="root">
<a class="include" href="#child"/>
</span>
</span>
At this point, we have reached a stable point and the remaining
includes are ignored because they reference ancestors.
I suppose if this discussion goes any further it should be moved to
the -dev list.
~Jason
_______________________________________________
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
