Interesting heuristic for table vs. dl HTML elements:

Rule of thumb: if you can put a header on the table version, it should not be a definition list.

Another rule of thumb: If you can not put a header on the table version, it should be a definition list.

This could also apply more broadly to thinking about:

• Whether things in a database should be in one table or separate tables, or whether an attribute/relationship is a singleton per entity, or if there can be multiple.
• Whether you should represent data on a webpage as a list, or a definition list, or a table, or whatever. For example, my current links page might be more semantically correct as a table instead of a list. (Maybe the same for posts and other pages.) I've been thinking recently about websites-as-materializations-of-data anyways, and leaning more into table elements makes that line of thought even more appealing.