include-pattern-issues - Revision history

Brian: Reverted edits by RoldrOnc4t (Talk) to last version by TobyInk

2008-12-20T21:07:42Z

Reverted edits by RoldrOnc4t (Talk) to last version by TobyInk

← Older revision		Revision as of 21:07, 20 December 2008
Line 1:		Line 1:
	~~getc4ta~~
	=Include-Pattern Issues=		=Include-Pattern Issues=

RoldrOnc4t: montroczel

2008-12-19T13:24:01Z

montroczel

← Older revision		Revision as of 13:24, 19 December 2008
Line 1:		Line 1:
			getc4ta
	=Include-Pattern Issues=		=Include-Pattern Issues=

TobyInk: /* Include-Pattern Issues */

2008-02-21T15:42:51Z

Include-Pattern Issues

← Older revision		Revision as of 15:42, 21 February 2008
Line 13:		Line 13:
	* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-21</span> raised by <span class="fn">[[User:TobyInk\|TobyInk]]</span></span>		* {{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">		<div class="description">
	** It's very easy for inclusions to end up as a loop. For example:		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>		<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.		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>
	</div>		</div>

TobyInk: Loops

2008-02-21T15:42:24Z

Loops

← Older revision		Revision as of 15:42, 21 February 2008
Line 7:		Line 7:
	<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. This is clarified on February 12th 2008, line 27 (http://microformats.org/wiki?title=include-pattern&diff=0&oldid=25677)		*# 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 a 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>
	</div>		</div>

BenWard: /* Include-Pattern Issues */ Marking Mike Kapley's issue closed

2008-02-12T03:02:45Z

Include-Pattern Issues: Marking Mike Kapley's issue closed

← Older revision		Revision as of 03:02, 12 February 2008
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>

AndyMabbett: {{issues-format}}

2008-01-14T11:08:28Z

← Older revision		Revision as of 11:08, 14 January 2008
Line 9:		Line 9:
	</div>		</div>
	</div>		</div>

			== Template ==

			{{issues-format}}

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

AndyMabbett: fmt

2008-01-14T11:08:05Z

fmt

← Older revision		Revision as of 11:08, 14 January 2008
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}}

Tantek: a few details

2007-08-03T20:38:31Z

a few details

← Older revision		Revision as of 20:38, 3 August 2007
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.''

MikeKaply: /* Include-Pattern Issues */

2007-08-03T20:29:35Z

Include-Pattern Issues

← Older revision		Revision as of 20:29, 3 August 2007
Line 2:		Line 2:

	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].
			*# ''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.''



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

AndyMabbett: related pages template, heading

2007-01-17T14:59:19Z

related pages template, heading

← Older revision		Revision as of 14:59, 17 January 2007
Line 1:		Line 1:
	[http://microformats.org/discuss/mail/microformats-dev/2006-May/000097.html A summary of issues with the include pattern].		=Include-Pattern Issues=

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

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