W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2012

[whatwg] Requests for new elements for comments

From: Matthew Wilcox <mail@matthewwilcox.com>
Date: Thu, 26 Jan 2012 21:45:07 +0000
Message-ID: <CAMCRKiJaJoQDGBzHsUnURO_bcEGfS36Zxt3ai1vrsGQrC5yYHQ@mail.gmail.com>
Obviously this is not right - perhaps I'm not understanding your use case?
Why would you want to specify an author as an attribute on the element?
What is wrong with:

<article class="by-post-author">
<p>Content</p>
<footer>
<p class="author">Written by: Person</p>
</footer>
</article>

Any time you do this the information will have been pulled through a CMS,
so it's trivial to have a class appended to the article. When would you
want this as pure HTML that's not been parsed by some form of CMS?

On 26 January 2012 21:43, Matthew Wilcox <elvendil at gmail.com> wrote:

>
> On 26 Jan 2012, at 20:47, Bjartur Thorlacius wrote:
>
> > ?ann fim 26.jan 2012 14:48, skrifa?i Matthew Wilcox:
> >> What's wrong with using a class on the <article> to identify the author
> >> stylistically? It's already identified semantically by having their name
> >> in the <article> itself, right (presumably in a <footer> too)?
> > As in <article class="asdf lolcats author-bjartur at spam.la>? Because
> then the class would contain content.
>
> Obviously this is not right - perhaps I'm not understanding your use case?
> Why would you want to specify an author as an attribute on the element?
> What is wrong with:
>
> <article class="by-post-author">
> <p>Content</p>
> <footer>
> <p class="author">Written by: Person</p>
> </footer>
> </article>
>
> Any time you do this the information will have been pulled through a CMS,
> so it's trivial to have a class appended to the article. When would you
> want this as pure HTML that's not been parsed by some form of CMS?
>
> > That would depend on a stylesheet containing the identifier of every
> poster on every page. Generating such stylesheets from content already
> marked up in a page in a nonstandard fashion seems hackish at best, and
> harmful to usability at worst.
> >
> > The situation only gets worse when you consider the different stylistic
> needs of various media. I might want the whole <footer> rendered to the
> relatively large desktop screen of mine, but omit everything but authors'
> name or identity on my handheld screen. <Address>, for example, should be
> hidden behind a menu button and the authors name displayed tersely.
> >
> > The best solution I can think of is stating normatively that hCard
> <footer>s describe authors of the respected article or document. hCard does
> not, AFAIK, provide means to state URIs of authors, but indirect
> identification using email addresses should suffice.
> >
> > <!DOCTYPE html>
> > <title>Example of Semantically Marking up Authors of Documents</title>
> > <article>
> > <h1>An Article Written by Bjartur</h1>
> > <p>This article was written to demonstrate how authorship might be
> marked up. I sure hope it's valid!</p>
> > <footer class="hcard">
> >  <a class="fn email" href="mailto:bjartur at spam.la">Bjartur
> Thorlacius</a>
> > </footer>
> > </article>
>
>
Received on Thursday, 26 January 2012 13:45:07 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:10 UTC