Hi Paul,
hAtom:content, hAtom:author and hAtom:contributor are all opaque [1],
that is, hAtom parsers must stop searching for hAtom content within
these elements.
Thus, you can safely nest a hCard side any of these elements without
worry of conflicts. There has been an issue raised [2] about hCards
appearing in other places. I'm not sure if it's a critical issue on
80-20 principles.
Regards, etc...
David
http://www.blogmatrix.com
[1] http://microformats.org/wiki/hatom#Nesting_Rules
[2]
http://microformats.org/wiki/hatom-issues#Opaqueness_of_other_microformat_elements
Paul Bryson wrote:
I'm just looking for extra confirmation of this little problem before
touching the wiki. It appears that hAtom uses the class attribute "title"
for it's title, such as what would go in a heading <hn> However, the hCard
also uses "title", but in a completely different context.
The problem arises if an hCard, which contains a "title", is located inside
of an hAtom, especially prior to the hAtom's "title". The specification
says:
* the first hAtom valid element with a class="title" is the Entry Title
hAtom valid meaning somewhere where we expect it (like not inside Entry
Content, for example).
* otherwise, the first hAtom valid <h#> element to appear in an hAtom
document is the Entry Title
* otherwise, the Entry Title is the empty string
Atom does not allow for an entry not to have a title.
It almost sounds like it cannot use a "title" from within the hCard, but it
isn't very clear. Is this wrong, or could someone provide clearer verbiage?
Atamido
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
