Re: maincontent element

On Mon, Sep 10, 2012 at 7:49 PM, Leif Halvard Silli
<xn--mlform-iua@xn--mlform-iua.no> wrote:
> Cameron Jones, Mon, 10 Sep 2012 17:53:23 +0100:
>> I was more implying that it is difficult for an author to
>> misunderstand the scope of what an article could be. As long as it's
>> "self contained" in some aspect it would seem to be a valid use.
>
> I don't have big problems with <maincontent> - but it is a bit long.
> Would you feel that <main> or <content> would invite to less
> "creativity" with regard to interpretation, than <maincontent> could
> lead to? They are also much more frequently used used as class/id names
> for such content than <maincontent>.
>

I have problems with any new top-level structural element until the
implementations of the current two have been seen in practice,
especially by document consumers.

All of the suggested ones are too generic to be used without
ambiguity, anything could be regarded as "content" or even "main".
HTML is a document-centric language so it lends itself to
document-centric terms, but the structural needs are catered for with
the ones that exist. After that, and the roles or class names provide
the necessary specificity and in a far more extensible and flexible
manner when all the needs of an application have been catered for.

>> Corollary to this, a document shouldn't have to contain an <article>
>> to give it definition, a <section> on it's own is a section within a
>> <body>.
>
> I guess, if the only content is the main content then <maincontent>
> doesn't add much.
> --
> leif halvard silli

Yes, it just seems unnecessary and already implied.

Thanks,
Cameron Jones

Received on Monday, 10 September 2012 18:59:34 UTC