I was recently trying to implement mark-up with both hListing (draft)
and hReview combined. For the most part the properties align except in
the case of 'DESCRIPTION'.
hListing: According to the schema, description is REQUIRED, makes no
assertion about detail or completeness of content marked up with
description.
hReview: “This optional field contains the full text representing the
written opinion of the reviewer”
The conflict here is that review specifies 'full text' whilst hListing
is permitting it to be used more loosely. But, if a piece of content is
marked up with both hListing AND hReview, even though the description is
optional in hReview, an hReview parser will not find 'full text' from
the description classname.
Since 'SUMMARY' is already claimed in hListing for the purposes of the
listing title, I'd like to solicit suggestions on resolving the conflict.
Thanks,
Ben
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
