Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)

 > ...
>> The problem can be fixed by stating once and for all the syntax for 
>> future elements.
> 
> That doesn't work. It would mean never introducing new void elements and 

... which I think is no problem at all ...

> never introducing new block-level elements. For example, in HTML5, it 
> would mean not introducing <command>, <event-source>, <section>, <nav>, 
> <aside>, <footer>, <header>, etc.

Could you please explain (or point to an explanation) why exactly it 
needs to be known beforehand whether something is block-level or not? 
It's certainly not needed for serializing a DOM, so I assume the parser 
needs to know for some reason?

> ...

BR, Julian