include-pattern-issues: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m (a few details)
Line 4: Line 4:


* {{OpenIssue}} 2007-08-03D raised by [http://www.kaply.com/weblog/ Mike Kaply].
* {{OpenIssue}} 2007-08-03D raised by [http://www.kaply.com/weblog/ Mike Kaply].
*# ''Issue 1: It needs to be explicit that the only classname on the object/etc should be include. Having classnames on the object is not necessary since the premise is that the object node is REPLACED by the referenced node.''
*# ''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.''





Revision as of 20:38, 3 August 2007

Include-Pattern Issues

See: A summary of issues with the include pattern.

  • open issue! 2007-08-03D raised by Mike Kaply.
    1. 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.


Related Pages