The style agenda

Bert Bos (bert@let.rug.nl)
Tue, 30 May 1995 21:15:40 +0200 (METDST)


Message-Id: <199505301915.AA262011341@freya.let.rug.nl>
From: Bert Bos <bert@let.rug.nl>
Subject: The style agenda
To: www-style@w3.org
Date: Tue, 30 May 1995 21:15:40 +0200 (METDST)

Now that the style list is officially open, it is time to think about
its agenda. Style sheets are very much needed on the Web, so we should
be very careful that we don't make any mistakes, because we probably
can't fix them later.

My intuition says that Arena's style sheets are heading roughly in the
right direction, although a number of details will need to change. But
I'd rather not trust intuition.

So I suggest that we collect some arguments pro and con the following
issues, before we start with the details of syntax and the list of
style properties. Now that the mailings are archived (thanks, Nick!),
we can refer back to those arguments when the full proposal is
written.

  1. Are we sure there is no existing language that we can copy?

  2. Do we agree on the goals as stated in the Cascading Style Draft[1]
     and the `Charter'[2]?

     For example: do the phrases "not SGML-complete" from the former
     and "useful subset of all possible SGML" from the latter
     contradict each other or not?

     In particular, do we agree on the fifth goal in the `Charter'[2],
     which states that the style language does not depend on the
     particular names of elements & attributes of HTML?

And, if we agree that a new language is needed:

  3. What is the (abstract) formatting model that we assume?

     For example: TeX uses `boxes & glue', DSSSL has a `page model &
     flow ojects', the simple model that I described[3] has a page
     model with five areas each of which is filled with a continuous
     stream of words. And how about non-visual media?

     A relatively high-level model is dangerous ("doesn't it exclude
     something important?") but useful, since it allows us to write
     translators to lower-level languages such as TeX.

  4. How powerful can/need we make the addressing scheme?

     Although the difference is small, I think my proposal[4] is more
     elegant, more powerful, and not more complex then H=E5kon's[5].

  5. How many levels of cascading priorities do we need?

     As a computer scientist, I would say that H=E5kon's three[6] is a
     strange number, I would rather have either two[7] or very
     many. (I consider `default' and `lens' as outside this range,
     since they need not use the same language.)

  6. How powerful can/need we make the expression language?

     We probably don't need things like macros right away, but
     numerical and other operators might be useful.[9]

And finally, we can invent a syntax (context-free, of course) and draw
up a list of style properties, being careful that we don't include
things that will make it impossible to add more powerful properties
later.

I'm sure we will encounter difficult decisions along the way. I've
already started a collection[8], though I hope that they will turn out
to be not so difficult after all.


Bert


[1]: http://www.w3.org/hypertext/WWW/Style/css/draft.html#goals
[2]: http://grid.let.rug.nl/~bert/Stylesheets/charter.html
[3]: http://grid.let.rug.nl/~bert/Stylesheets/model.html
[4]: http://grid.let.rug.nl/~bert/Stylesheets/addressing.html
[5]: http://www.w3.org/hypertext/WWW/Style/css/draft.html#addressing
[6]: http://www.w3.org/hypertext/WWW/Style/css/draft.html#cascading
[7]: http://grid.let.rug.nl/~bert/Stylesheets/cascading.html
[8]: http://grid.let.rug.nl/~bert/Stylesheets/unsolved.html
[9]: http://grid.let.rug.nl/~bert/Stylesheets/expr.html

-- =

                          Bert Bos                      Alfa-informatica
                 <bert@let.rug.nl>           Rijksuniversiteit Groningen
    <http://www.let.rug.nl/~bert/>     Postbus 716, NL-9700 AS GRONINGEN