[uf-dev] Re: [uf-new] Microformats parsing,
in general (was: hAudio final draft)
Scott Reynen
scott at randomchaos.com
Tue Jun 19 15:55:30 PDT 2007
On Jun 19, 2007, at 4:04 PM, David Janes wrote:
>> >> 1. Scope-less approach to parsing.
>> >
>> > This is why I've been picking at this like a scab for the last
>> week. I
>> > don't think we've adopted #1 at all.
>>
>> How do I limit the scope of an hCard URL to
>> the contact (and not the event)?
>
> As briefly mentioned earlier in the thread -- I think hcard and
> hcalendar should probably always be mfo, which would deal with this
> problem.
>
> Even if they weren't, you could explicitly mark them as "mfo"
I'm a bit confused by this thread now, but it seems we agree that the
current inability of publishers to indicate scope is a problem, and
MFO is a potential solution. Is that correct? If so, I think we
need to openly discuss the semantics of MFO (i.e. follow the process)
before we get into a more limited discussion of how to parse MFO. I
don't think it's ready to parse at all yet, so I'm not sure why it's
on -dev.
Peace,
Scott
More information about the microformats-dev
mailing list