This argument becomes a little silly ... Nobody seems to suggest that tables be used for layout without meaning, only that the given example data is tabular and therefore should be displayed in the table. Therefore, I see no reason to post links to the table layout when it becomes clear that everyone who participated in this discussion went back years.
According to BalusC, data can be correctly displayed in the definition list. This, of course, produces a more elegant layout, but whether it will be more semantically correct is (obviously, from this discussion) debatable. I do not know the definitions of tabular data that preclude this use, including OED! Thus, using a table for this data, as prodigitalson says, is also perfectly acceptable.
Robert Grant - could you provide a link that defines the table as data, which requires two labels to identify it? I do not know this definition, but I am ready to learn. I am a bit confused as to how using spacing in a div is more semantically valid than a table. Or however semantic it may be. Both are meaningless tags.
The markup used should establish the relationship between the key-value pairs. Only a table or dl can do this.
The example markup for a table is quite simple (since there is no need for anad btw, the tbody tag is not needed, since there are no other table elements for differentiation). Screenshots require a screenshot = "string" for tags, but in addition to the caption.
Having said all this, the whole point here is to help someone solve the problem. The nature of this problem tends to indicate that garj is not an advanced front-end developer and that their css skills cannot be at the highest level. For me, this means using a table solution is preferable. Stacking dl in a way that gracefully degrades in any browser with a significant market share is by no means a trivial task.
user228135
source share