StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9205174
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-09T03:52:20.490
FavoriteCount
0
LastActivityDate
2012-02-10T08:28:44.650
LastEditDate
2012-02-10T08:28:44.650
LastEditorUserId
230649
OwnerUserId
230649
ParentId
6949831
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
The W3C spec leaves a lot open to interpretation and it ultimately comes down to the author's opinion. Here is a short and simple answer in the form of a question: What are the primary significant pieces of content you want to share on the page? Here are a few examples: <ul> <li>On this very page, each answer could be an article.</li> <li>On flickr each photo displayed in the photostream could be considered an article.</li> <li>On dribbble each shot displayed on the page could be an article.</li> <li>On google each search result listed could be an article.</li> <li>On a blog each article.. well each article could be an article.</li> <li>On a blog page with an article and a series of comments you could have two major sections. One with an article and another for comments in which each comment could be considered an article.</li> </ul> It's the author's discretion as to how far they want to go. Most blog authors have an RSS feed for their articles, but others may also provide feeds for comments, and shared links. A lot of people have written on this subject. For further information I highly recommend reading: <ul> <li><a href="http://html5doctor.com/the-article-element/" rel="nofollow">http://html5doctor.com/the-article-element/</a> (you've already shared this)</li> <li><a href="http://www.impressivewebs.com/html5-section/" rel="nofollow">http://www.impressivewebs.com/html5-section/</a></li> <li><a href="http://www.iandevlin.com/blog/2011/04/html5/html5-section-or-article" rel="nofollow">http://www.iandevlin.com/blog/2011/04/html5/html5-section-or-article</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHTML5 - Correct usage of the <article> tag
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJim Jeffers
UserOwnerUserId
1. USJim Jeffers
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHTML5 - Correct usage of the <article> tag
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.