W3C home > Mailing lists > Public > www-html@w3.org > November 2003

Re: Accessibility in XHTML 2.0 Draft - Tables

From: David Woolley <david@djwhome.demon.co.uk>
Date: Mon, 3 Nov 2003 21:43:13 +0000 (GMT)
Message-Id: <200311032143.hA3LhDt09424@djwhome.demon.co.uk>
To: www-html@w3.org

> I had a few extra considerations for creating sections within a <table>
> structure, since that would be a little more complex than just

Complex versions of this were discussed only last week.

However, it seems to me that what you are trying to do is within the
domain of style sheets; you are creating an alternative partitioning of
the structure based on media limitations, not providing a logical
breakdown of the document structure.  If you were breaking down the
document structure, many of the existing mechanisms would already 

> would have to make special considerations.  One rule you might have for
> sections is that if you begin an element within a <section> you have to

You *must* have this rule as it would be a violation of XML (not well
formed) and a violation of SGML (for HTML) not to strictly nest elements.
However, you have still compromised the structuring by allowing an element
to be interposed anywhere; you can't write sensible content model 
constraints, particularly in XML, which doesn't allow exclusions, if an
element is allowed as a child of everything and a parent of everything.

> end the element within the <section>.  For example, something like this
> wouldn't be allowed:

A conforming XHTML browser would reject the whole page if you tried, although
see another thread for the reality of conforming parsers.
Received on Monday, 3 November 2003 17:46:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:06 UTC