W3C home > Mailing lists > Public > www-style@w3.org > February 1997

RE: Positioning HTML Elements with Cascading Style Sheets

From: Steve Knoblock <knoblock@worldnet.att.net>
Date: Tue, 04 Feb 1997 00:03:46 -0500
Message-Id: <2.2.32.19970204050346.00709fc8@postoffice.worldnet.att.net>
To: bosak@atlantic-83.Eng.Sun.COM (Jon Bosak), www-style@w3.org
John,

>DSSSL very definitely is not.  DSSSL is entirely functional and
>entirely side-effect-free.  Nothing ever happens in a DSSSL

That would ease some misgivings about DSSSL being more 'script-oriented'.
From what I've seen it is a reasonable approach that authors could work
with. I would probably use DSSSL if it were widely deployed, perhaps in
parallel with CSS and other style languages to give a full range of choices
to the browser. As primarily an author/publisher of my own web site, I am
concerned only with the best way to present my content. I'm not tied to any
one implementation.

>stylesheet.  The stylesheet is one giant function whose value is an
>abstract, device-independent, nonprocedural description of the

I have to admit the DSSSL model is intriguing. The samples posted here have
been quite interesting.

>* Generate a table of contents at this spot.
>

>These aren't contrived or artificial examples; they're dirt-normal
>commercial publishing.  Without programming, you can't handle even the
>last one.
>

I agree they are real tasks in publishing. But should they be generated as
they are rendered or as they are authored? Should a style language be
generating or manipulating content?

Steve

 -:-     City Gallery ed.- http://www.webcom.com/cityg  PhotoGen list admin.
 -:-     Steve Knoblock,  knoblock@worldnet.att.net
 _/     Member:  Natl. Stereo. Assoc. http://www.tisco.com/3d-web/nsa/nsa.htm
Received on Tuesday, 4 February 1997 00:03:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:53:49 GMT