StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12154299
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-08-28T07:01:33.050
FavoriteCount
0
LastActivityDate
2012-08-28T07:01:33.050
LastEditDate
LastEditorUserId
0
OwnerUserId
1626018
ParentId
5689438
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
You basically asked two questions: If it's semantically correct your example and if you can nest fielset elements. Some answers given here were wrong. It is syntactically correct, but not semantically correct and you can nest fieldset elements. It is not semantically correct for the very reason that a form it's not a presentational element. Tables are used to display information in rows and columns where you clearly not doing that. A table is not a prop for making good your form and this is how you used it. Some suggestions you may follow come next. Referencing the HTML5 standard, I quote from the proposal document: "Each part of a form is considered a paragraph, and is typically separated from other parts using p elements." <a href="http://dev.w3.org/html5/spec/single-page.htm" rel="noreferrer">http://dev.w3.org/html5/spec/single-page.htm</a> section 4.10 <a href="http://dev.w3.org/html5/spec-LC/forms.html" rel="noreferrer">http://dev.w3.org/html5/spec-LC/forms.html</a> Should answer the nesting question as well. The question, I guess, arise from the wish of knowing how to section form content. The answer is with fieldsets. The form itself has a meaning, so "yes", it will be a fieldset that will contain all form elements (and it may be disabled). Coming back to your example, you will have a fieldset for "registration" and sections of the registration grouped by nested fieldsets, as one such section in your example is the "address". The "better" way of making a form... it depends and I guess it is another question that will remain open to debates until the HTML5 will be ready and implemented correctly in all browsers.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POnested fieldsets
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFlorin Sima
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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.