On Fri, Feb 27, 2009 at 5:51 AM, Jeremy Keith <jer...@adactio.com> wrote: > Ted wrote: >> >> Yup, it's perfectly valid. > > André wrote: >> >> My gut also told me this was valid. I even implemented hatom this way >> in my blog. > > Good stuff. > >> After I read this thread, I went to check and lo and behold... >> Operator transforms the author part of hatom into this: >> >> object author { >> 0=posted by André Luís >> } > > Yes, this is one of the things that prompted my question. I noticed that on > Huffduffer, Operator was extracted "author" as the whole string: > > object author { > 0=—Huffduffed by adactio 11 hours ago > } > >> So I guess Operator is lacking this "cleverness". It apparently >> doesn't treat the author vcard as vcard, but as a property of hentry. > > Right ...which is technically what the spec says but I guess the spirit of > the spec would be to extract hCard *properties* (n/fn, url, email, etc. — as > Optimus does) rather than extracting everything between the opening and > closing "vcard" containing elements. > > Perhaps I should an example to the hAtom examples page to show this usage of > the author property.
Is this not though, just a general property of microformats in general? I.e. that the semantic information is being encoded at the property level and bundled at the the h* level. Regards, etc... -- David Janes Mercenary Programmer http://code.davidjanes.com _______________________________________________ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss