( Conversation started here, with @murtaugh and @zeldman. )
Ah man, I got Opinions™ on this. I ususally go with something like:
<aside>
<h1>Optional Heading</h1>
<blockquote>
<p>It is the unofficial force—the Baker Street irregulars.</p>
</blockquote>
<address>Sherlock Holmes</address>
<cite>Sign of Four</cite>
</aside>
aside
provides sectioning context, address
flags the author/owner of the current sectioning context, cite
to cite a “work”, and blockquote
because it’s… a blockquote. I’d probably bolt the emdash onto the front of the address
with address:before { content: "—"; }
, where it’s not really essential. This is all predicated on the pullquote being considered non-essential to the surrounding content.
The figure
route could work too, but technically figure doesn’t provide sectioning context, so there’s two ways you could go with this.
<aside || section>
<figure>
<blockquote>
<p>It is the unofficial force—the Baker Street irregulars.</p>
</blockquote>
<figcaption>
<address>Sherlock Holmes</address>
<cite>Sign of Four</cite>
</figcaption>
</figure>
</aside || /section>
aside
if complementary but inessential to the surrounding content (like a pull-quote directly from the article), section
if part to the surrounding content (an external quote directly referenced by the text).
That’s an awful lot of stuff, though, so the other way of doing it with figure:
<figure>
<blockquote>
<p>It is the unofficial force—the Baker Street irregulars.</p>
</blockquote>
<figcaption>
<p>Sherlock Holmes</p>
<p>Sign of Four</p>
</figcaption>
</figure>
The figcaption
flags the content as metadata for the rest of the figure, but you lose the specifics: “author” and “work” just become generic metadata.
I’m partial to the first one from an HTML5 outline standpoint.
Apologies for butting in, but this entire conversation seems bizarre, and I feel like you might be an example for others, so for the sake of the entire interwebs, I am forced to offer some sort of sensical intercession.
First, a blockquote is a quote that is more than four lines long that appears in the body of a work. So, semantically, if that's what you're aiming for, you would never use a blockquote for an aside. And you definitely wouldn't use figure.
Second an aside can be anything that does not appear in the main body of the work. Anything. It can be a pullquote, a chart, a sidebar, a whatever. Semantically, a blockquote would never appear in an aside as a pullquote.
For semantic purity, a blockquote would appear between two paragraphs:
In proper "style", the cite would be included as text within the preceding paragraph. To connect the citation to the blockquote you have the cite attribute. If, for stylistic reasons, you would like the cite to be repeated beneath the blockquote, then using figure is total bullshit. You want section.
That is a semantically pure blockquote.
Pullquotes are a different beast. Semantically, they are nothing. They are visual fluff designers use to add emphasis and move the eye around the screen in a pleasing manner. They have nothing to do with the content and can be removed, wholesale, with no impact on the content. So, for example, for small screens, you might hide pullquotes entirely.
You wouldn't create pullquotes using figure. Figure is something more akin to a footnote. Footnotes are not critical to the content, but they carry more meaning than pullquotes. Hell, they carry meaning. Puyllquotes HAVE NO SEMANTIC MEANING. So, that leaves aside for pullquotes. A semantically pure pullquote would look like this:
It can go before your content, after your content, or in the middle. Who cares. It has no semantic meaning.
You'll notice no cite. That's because the pullquote is a quote pulled from the content you're currently reading. You don't need a citation. You'll also notice there's no q or blockquote. Q and blockquote are used to flag when you are using someone else's words in your work. A pullquote is your words from your work. Semantically, you do not need to identify the quotation. If, for visual style reasons, you would like your pullquotes to have visual quotation marks around them, and you don't want to actually type ̶x, then use content :before and :after.
So... that's how you use blockquote with semantic correctness. And that's how you create a semantically correct aside.