- From: Paul Prescod <papresco@calum.csclub.uwaterloo.ca>
- Date: Sun, 15 Jun 1997 01:36:05 -0400
- To: w3c-sgml-wg@w3.org
Jon Bosak wrote: > (No > cascading rules have been defined for DSSSL, but there seems to be > nothing preventing this at some time in the future.) I have to disagree with half of the above statement. Which half depends on your definition of "cascade". If you define "cascade" to mean "grab characteristics from construction rules from various places and merge them into a single construction rule" (as in CSS) then I would disagree that DSSSL could ever have such a thing without doing violence to its fundamental concepts. How do you merge the characteristics from a "table" flow object and a "literal" flow object into something reasonable? If you define "cascade" more broadly to mean "allow definitions to conflict, and have a specified mechanism for resolving conflicts" then DSSSL already has a cascading mechanism: "A process specification shall be processed by first processing the declarations of all of the parts, and then processing the bodies of all of the parts in order. Within a single part, there shall not be conflicting declarations; when two declarations in different parts conflict, the declaration in the earlier part shall take precedence. Similarly, within the body of a single part, there shall not be conflicting specifications, but when two specifications in the bodies of different parts conflict, the specification in the earlier part shall take precedence." Paul Prescod
Received on Sunday, 15 June 1997 01:36:18 UTC