> [Original Message]
> From: Lachlan Hunt <lachlan.hunt@iinet.net.au>
>
> Ernest Cline wrote:
>
>    Assuming the distinction is only presentational, since <blockquote> 
> can now be used within <p> just like <quote>, would it really matter 
> whether or not it was a quote was block or inline?  Although 
> <blockquote> currently can't be used within other inline elements, like 
> <quote> can, this may only be a minor difference, and thus it still may 
> not matter whether the quote is block or inline.  If this is the case, 
> then, obviously, we'd only need the one element.  Also, as you suggested 
> in an earlier post, the content model could be:
>
> > (Block*) | (PCDATA|Inline)*
>
>    Which solves the problem of mixing other block and inline elements
like:
>
> <quote><strong>inline text</strong>
> <p>paragraph text</p></quote>
>
> because it restricts the author to having only block, or only inline 
> content, thus kind of making a distinction between block and inline 
> quotes, but without the need for two elements.
>    (I am however aware of the current styling problems of not being able 
> to apply style based on an elements children, but this could be handled 
> by an author with appropriate classes, but that doesn't help the default 
> styling by UAs.  I'll have to think about this some more.)

Nope, because assuming that the block/inline distinction remains so that
we have certain elements such as <span> that can only have inline
content inside them then if <quote> was used for either block or inline
we could have <span><quote><div/></quote></span> as I believe there
does not exist in XML a mechanism for telling <quote> that inside a <span>
certain elements such as <div> are not OK while they are OK elsewhere.

<quote> doesn't need the block/inline distinction for itself, but if it is
needed for other elements there will be a need for two separate
quotation elements for the block and inline models.