table-examples: Difference between revisions
Jump to navigation
Jump to search
(HTML link to W3C) |
m (Reverted edit of UjfPwk, changed back to last version by Phae) |
||
| (13 intermediate revisions by 8 users not shown) | |||
| 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. | = Table Examples = | ||
As the first stage of the microformats [[process]], this page collects [[examples]] of best/common practice for using the [http://www.w3.org/TR/REC-html40/struct/tables.html table] tag to represent structured data. | |||
= | == 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) | |||
= | == Participants == | ||
* [http://www.opendarwin.org/~drernie/ Dr. Ernie] | |||
= | == Real-World Examples == | ||
* [http://www.456bereastreet.com/archive/200410/bring_on_the_tables/ Best practices] for marking up tabular data (especially for accessibility) | |||
** < th scope=col|row id="name"> for headers | |||
** caption, summary | |||
= | == Existing Practices == | ||
== Proposal (N/A) == | |||
== See Also == | |||
* [http://www.w3.org/TR/REC-html40/struct/tables.html HTML 4.0 tables] | |||
* [http://www.w3.org/TR/2004/WD-xhtml2-20040722/mod-tables.html XHTML 1.0 tables] | |||
* [http://www.w3.org/TR/2004/WD-xhtml2-20040722/mod-tables.html XHTML 2.0 tables] | |||
Latest revision as of 19:43, 12 August 2007
Table Examples
As the first stage of the microformats process, this page collects examples of best/common practice for using the table tag to represent structured data.
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)
Participants
Real-World Examples
- Best practices for marking up tabular data (especially for accessibility)
- < th scope=col|row id="name"> for headers
- caption, summary