W3C home > Mailing lists > Public > www-style@w3.org > May 2010

Re: A review on CSS3 module dependencies

From: Christoph Päper <christoph.paeper@crissov.de>
Date: Thu, 6 May 2010 10:14:28 +0200
Message-Id: <C0275FEC-1C8F-401A-ABB2-36190B0F335C@crissov.de>
To: CSS <www-style@w3.org>
Eduard Pascual (2010-04-11):
> I have been looking at dependencies between CSS3 modules for a while, and found out that they form a rather complex graph with several inconsistencies and circular dependencies.

The transition from a monolithic spec towards a modular collection of related, but rather independent specs surely ain’t easy. To make it easier I believe CSS modules should only rely on other CSS modules (and possibly external specs). That means no references to level 1, 2 or 2.1, except each level 3 module in working draft state should reference the exact parts of CSS2 or CSS21 it builds upon. It thereby defers dependencies from other modules until it has reached a reasonably stable state, CR probably, and therefore can act as a normative reference itself. The referencing module doesn’t have to be updated until the other module has reached a stable state in a higher level, e.g. 4. Basically the same applies when a module is split into two newer ones or – and I’m not as sure about this case – combines two older ones.

> Just in case it's useful, I'm attaching a SVG version of GraphViz's output,

It is useful, thanks, but actually I would have liked the source better.
Received on Thursday, 6 May 2010 08:15:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:45 UTC