The inability for tables to deal with data that span multiple rows, especially in situations where the screen space is limited is one particular reason why list views have been used as an alternative to display information. The popularity of the flat/metro design that uses the card/tile style of information display has also resulted in the use of list view to display more complex data.
While the use of tables are well defined in terms of the data structure and implementation details, the specifications of a list view seems to be less detailed. Some list views are static like a table while others can trigger additional information to be displayed. Also the hierarchy levels of list views can vary considerably while tables generally have the header row and data rows.
Apart from the implementation issues that have been dealt with on StackOverflow and specific accessibility issues, are there any other considerations when it comes to choosing between list or table design?
Are they considered logical equivalents (so it is a matter of visual or cognitive processing preference) or do they cater for specific types of information display (in which case we should provide better guidelines for when we should use which type)?
A related question about Tile versus List/Table view provides some interesting ideas as well.