I've updated hcard parsing to handle AREA for email, URL, and other properties:
http://microformats.org/wiki/hcard-parsing Note that since AREA is an empty element, the rules are slightly different than for A. Brian, let me know if you think this will be anything more than trivial for X2V to implement. As far as the MAP element is concerned, if folks want to explore how they would use the MAP element in real world examples, I encourage you to do so, and report back on your experience, much as Michael and Scott did with AREA. Thanks, Tantek On 6/8/06 11:40 AM, "brian suda" <[EMAIL PROTECTED]> wrote: > I have started to look into the AREA element[1] as another semantic > element similar to 'A'. > > The AREA element can take a class attribute and must be a child of a MAP > element. MAP elements can have a mix of AREA and Block Level elements. > > There are a few minor things that should be addressed. > 1) Are we discussing the semantics of MAP or AREA? (abit rhetorical, but > best to be stated in writing) > 2) If we are talking about adding classes to MAP (similar to adding > classes to OL UL) then there are all sorts of issues, such as overlaping > coordinates, ordering, etc. > > Otherwise i don't see much of a difference in AREA vs A, and this can > easily be accounted for in parsers by following the same rules as an 'A' > element would. > > -brian > > [1] - http://www.w3.org/TR/html4/struct/objects.html#h-13.6.1 > > Ryan King wrote: >> On Jun 7, 2006, at 9:31 PM, Michael Leikam wrote: >>> --- Scott Reynen <[EMAIL PROTECTED]> wrote: >>>> It turns out the emails aren't being parsed even after >>>> the inclusion >>>> is done with the root referenced node. I believe this is >>>> because >>>> you're putting them in <area> tags, and the hcard spec >>>> only allows them to be put in <a> tags >>> >>> Is there a reason <area> tags ought not to be supported? >>> They strike me as semantically equivalent to <a> tags. >> >> Well, you're the first person to ask for them. :D >> >> At first thought, I don't see why not, but it might require some more >> research. >> >> -ryan >> _______________________________________________ >> microformats-discuss mailing list >> [email protected] >> http://microformats.org/mailman/listinfo/microformats-discuss >> > > _______________________________________________ > microformats-discuss mailing list > [email protected] > http://microformats.org/mailman/listinfo/microformats-discuss _______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
