table-examples: Difference between revisions
Jump to navigation
Jump to search
(HTML link to W3C) |
|||
Line 1: | Line 1: | ||
As the first stage of the microformats [[process]], this page collects [[examples]] of best/common practice for the [http://www.w3.org/TR/REC-html40/struct/tables.html table] tag. | As the first stage of the microformats [[process]], this page collects [[examples]] of best/common practice for the [http://www.w3.org/TR/REC-html40/struct/tables.html table] tag. | ||
= | = The Problem = | ||
Thought often abused for layout, the original purpose of HTML tables is to provide a two-dimensional structure for data. The purpose of this exploration is to determine if there are common patterns for annotationg those structures, and (if so) whether there is a need to formalize that as a microformat (a la [[xoxo]] for lists). The working hypothesis is tables typically represent two kinds of data: | |||
* a list of dictionaries (with column headers, and sometimes row headers) | |||
* a grid of numerical data (without any headers, or merely numeric indices) | |||
= Examples on the Web today = | = Examples on the Web today = |
Revision as of 16:32, 6 October 2005
As the first stage of the microformats process, this page collects examples of best/common practice for the table tag.
The Problem
Thought often abused for layout, the original purpose of HTML tables is to provide a two-dimensional structure for data. The purpose of this exploration is to determine if there are common patterns for annotationg those structures, and (if so) whether there is a need to formalize that as a microformat (a la xoxo for lists). The working hypothesis is tables typically represent two kinds of data:
- a list of dictionaries (with column headers, and sometimes row headers)
- a grid of numerical data (without any headers, or merely numeric indices)