<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Semantics of Article Headline and&#160;Byline</title>
	<atom:link href="http://konstruktors.com/blog/web-design/1779-semantics-of-article-headline-and-byline/feed/" rel="self" type="application/rss+xml" />
	<link>http://konstruktors.com/blog/web-design/1779-semantics-of-article-headline-and-byline/</link>
	<description>Web Design, WordPress and Performance Services</description>
	<lastBuildDate>Wed, 01 Feb 2012 16:50:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19904</generator>
	<item>
		<title>By: Andrew</title>
		<link>http://konstruktors.com/blog/web-design/1779-semantics-of-article-headline-and-byline/#comment-1134</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 15 Dec 2009 12:11:30 +0000</pubDate>
		<guid isPermaLink="false">http://konstruktors.com/blog/?p=1779#comment-1134</guid>
		<description>It depends on whether you are using HTML 5 in which case you can surround the entire post in an article container. That might go some way to making it less sematically problematic.

Even in that case though a header is a hierachical indicator, so just as an h2 subdivides the article in a way that you can&#039;t break back out of (all content after that point is a sub-section, or sub-sub-section etc) the H1 signals that everything that follows is content under that title.

In most cases the date and attribution, while not part of the article itself, is part of the content that falls under that header so you would expect it to be positioned after the header.

Placing the date and attribution before the header effectively renders it applicable to the content that comes before the header, or to the page in general; although again, you would expect the H1 tag to apply to the page unless using further semantic divisions as is possible in HTML 5.</description>
		<content:encoded><![CDATA[<p>It depends on whether you are using HTML 5 in which case you can surround the entire post in an article container. That might go some way to making it less sematically problematic.</p>
<p>Even in that case though a header is a hierachical indicator, so just as an h2 subdivides the article in a way that you can&#8217;t break back out of (all content after that point is a sub-section, or sub-sub-section etc) the H1 signals that everything that follows is content under that title.</p>
<p>In most cases the date and attribution, while not part of the article itself, is part of the content that falls under that header so you would expect it to be positioned after the header.</p>
<p>Placing the date and attribution before the header effectively renders it applicable to the content that comes before the header, or to the page in general; although again, you would expect the H1 tag to apply to the page unless using further semantic divisions as is possible in HTML 5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raimonds</title>
		<link>http://konstruktors.com/blog/web-design/1779-semantics-of-article-headline-and-byline/#comment-1133</link>
		<dc:creator>Raimonds</dc:creator>
		<pubDate>Tue, 15 Dec 2009 10:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://konstruktors.com/blog/?p=1779#comment-1133</guid>
		<description>Well, I think it&#039;s not appropriate because H1 suggests that it semantically &lt;em&gt;wraps&lt;/em&gt; the content that follows afterwards. Bringing article date and credits before the H1 tags drags them out of context. One may argue that article credits are not part of the post and there is a point in that. But my opinion is that article credits do belong with the post as article without contextual credits is a half baked one (&lt;em&gt;semantically&lt;/em&gt;, that is).</description>
		<content:encoded><![CDATA[<p>Well, I think it&#8217;s not appropriate because H1 suggests that it semantically <em>wraps</em> the content that follows afterwards. Bringing article date and credits before the H1 tags drags them out of context. One may argue that article credits are not part of the post and there is a point in that. But my opinion is that article credits do belong with the post as article without contextual credits is a half baked one (<em>semantically</em>, that is).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
