Re: The concept of cascading

It seems to me that the department that wants to implement red
underlinesfor links can do that
by creating a DSSSL style sheet from scratch (or by copying and modifying
the company standard one).

I can think of two things that might prevent this. First, a company policy
saying which things
you can and can't modify. The second is that it is hard to modify DSSSL
style sheets.

The first method works with CSS also (although CSS doesn't provide a way to
specify in the 
stylesheet, which things policy allows you to update. The other is security
by obscurity,
which in my opinion is not much security at all.

At 01:12 PM 4/29/97 -0400, Paul Prescod wrote:
>> Seems simpler to manage and no less controllable than parameter-passing
>> to activate a program stub.
>How so? This is what I mean by a stub:
>(define departmental-logo "http://foo.bar.com/department/graphic.gif")
>(define departmental-background (color rgb 0 0 0))
>(define departmental-table-of-contents-style
>    ; some hairy code to generate the world's most beautiful TOC
>(declare-initial-value "Helvetica")
><stylesheet use="base-company-spec.dsl">
>I don't see that as being difficult to manage, and I do see it as being
>highly controllable because the set of things that can be defined are 
>declared in advance. I'll admit, however, if you want unconstrained
>changes with no need for forethought on the part of the people creating
>the base stylesheet, then CSS is better. But then you can run into the 
>problem of: "can we add a red underline to our stylesheet? I dunno 
>if anyone has changed their background to red, or perhaps changed the 
>link colour to red."
>For small companies that is probably not a problem and the CSS mechanism 
>would be simpler than the DSSSL mechanism.
> Paul Prescod