[uf-dev] Re: [uf-new] Microformats parsing, in general (was: hAudio final draft)

[David Janes]

On 6/19/07, Scott Reynen <scott at makedatamakesense.com> wrote:
> On Jun 19, 2007, at 8:14 AM, David Janes wrote:
>
> >> 1. Scope-less approach to parsing.
> >> 2. Requirement to heavily re-use class names.
> >
> > 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.
>
> I'm publishing a website with events marked up in hCalendar.  Each
> event has attendees, marked up in hCard.  The attendees have URLs,
> but the event does not.  How do I limit the scope of an hCard URL to
> the contact (and not the event)?  Here's a real world example of this
> problem:
>
> http://playinghere.com/2007/07/21/LA/New_Orleans/The_Parish/
>
> As far as I can tell, the current answer is that I can't do that, and
> it's not a big deal because the contact URL is somewhat relevant to
> the event.  But as a publisher, I don't like that  I can neither
> control nor predict how my events will be parsed.

[moved to microformats-dev]

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"

Regards, etc...

-- 
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
http://blogmatrix.blogmatrix.com