[uf-dev] include-pattern testing
brian.suda at gmail.com
Mon May 1 12:03:27 PDT 2006
Ryan King wrote:
> On Apr 29, 2006, at 11:02 AM, Tantek Çelik wrote:
>> On 4/29/06 9:40 AM, "Brian Suda" <brian.suda at gmail.com> wrote:
>>> 2) The easy fix would be to lobby to change th include-pattern so that
>>> the #ref-id acts like a 'root node' and we only look to the children
>>> of that (the way X2V currently works)
>> I am open to this change, I don't think it would break the examples
>> we have.
> I don't think so.
> In the wiki example (re: James Levine), the <object> refers to #j,
> which is the .fn.n of the main hCard. If we were to change things so
> that the include pattern only looked at children, that example would
> either need to add another layer of markup (around the .fn.n) or the
> include-pattern would have to refer to the entire hCard. I don't think
> this is as convenient.
> I think the ability to point straight at the element to be included is
> a feature worth having, even if it makes parsing more difficult.
Then this becomes true
<object class="vcard agent fn include" id="self" data="#self"
now what does that mean? I found a vcard, and an include, so i go fetch
the data, which is fn, agent vcard and include? I know we can avoid the
whole recursive portion, but we are now flattening out 'vcard and fn'
and giving ambiguity to agent?
I agree that not pointing directly to the data with the #id-ref, but to
it's parent is not as convenient, but i think from a parsing "include"
perspective it is needed.
More information about the microformats-dev