Edward,
My gut also told me this was valid. I even implemented hatom this way
in my blog.
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
}
Which is not what I wanted. I have
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 {
David wrote:
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.
Yes. But with all the examples on the hAtom examples page, that isn't
clear (for the hCard bit) so I
On Thu, Feb 26, 2009 at 5:59 PM, Jeremy Keith jer...@adactio.com wrote:
I have a question about the author property in hAtom...
The spec says that author is modelled on the Atom AUTHOR element (
http://atomenabled.org/developers/syndication/#requiredFeedElements ) and
must be encoded as an
I have a question about the author property in hAtom...
The spec says that author is modelled on the Atom AUTHOR element ( http://atomenabled.org/developers/syndication/#requiredFeedElements
) and must be encoded as an hCard.
Now, here's an example of a perfectly valid hCard:
p
Now, here's an example of a perfectly valid hCard:
p class=vcardHello, my name is span class=fnJeremy Keith/span./p
So my question is: is this valid for hAtom?:
p class=author vcardHello, my name is span class=fnJeremy
Keith/span./p
Yup, it's perfectly valid.
