On 20 Apr 2005, at 7:53 pm, Thomas Broyer wrote:
I'd expect my feed and entry titles not to be block-content but rather inline content, so a div wouldn't be an appropriate container regarding its structural meaning.
Let me stop you right there. The first thing to note is that the div is trivial to add and will be discarded straight away by the consumer. Therefore:
- It does not change the meaning of the fragment
- It is not hard to do
Therefore we can conclude the cost, even to people that don't need it, is essentially zero.
People wanting containers to carry their XHTML namespace declarations (in order to produce prefix-free documents) can choose among the inline-level span or the block-level div elements. If their content is already in a container (e.g. a single paragraph summary), they can use it as the xmlns holder.
This is exactly the benefit of the required and then discarded div. Without it, a significant proportion of users has to add chuff within their content that may change its meaning.
Graham
