Keith Alexander wrote: > > On a related note, can anyone confirm that @content is intended purely > for machine-readable content? (ie: will it suffer the same problems as > using @title has in microformats, or not?)
Yes, it is intended purely for machine-readable content. It is there for those cases where we must sadly give up on DRY (Don't Repeat Yourself), e.g. on timestamps, and have different machine-readable and human-readable versions of the data. -Ben
