On Oct 10, 2007, at 4:48 AM, [EMAIL PROTECTED] wrote:
Clearly identifying those "other things" would probably help. What
exactly is the problem we're trying to solve here?
When the content is in a pre tag, there can be issues with word-
wrapping, or not wrapping as the case may be.
The purpose of the pre tag is to say that the spacing is
predefined, within the content of the pre element itself.
When there is no special spacing, which is the case for a majority
of poetry, the use of the pre tag becomes redundant.
Using linebreak tags or other structures provide additional
structural information about the content that isn't available with
pre tags.
And, we should be able to apply class names to whatever code
structure we are currently using for poetry, rather than
restricting everyone to using a certain element.
These are the issues I have with using the pre tag to markup all
poetry.
Sorry, that didn't really answer my question at all. Why do you want
to apply class names to your poetry in the first place? What's the
problem you're trying to solve with that? We should avoid wasting
our time on semantics for semantics' sake.
--
Scott Reynen
MakeDataMakeSense.com
_______________________________________________
microformats-new mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-new
