Re: The value of navigability
gtn@ebt.com (Gavin Nicol)
Errors-To: listmaster@www0.cern.ch
Date: Tue, 7 Jun 1994 18:18:16 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9406071614.AA17987@ebt-inc.ebt.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: gtn@ebt.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: gtn@ebt.com (Gavin Nicol)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: The value of navigability
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Dave Raggett writes:
>I think we ought to bite the bullet and support SGML's marked sections.
>This allow you to switch on/off sections of a document with simple entity
>declarations that can be set in the <!DOCTYPE> declaration or set by
>client-side scripts or user preferences. It is too late to do this for
>HTML 2.0, but I see no reason why HTML 3.0 compliant browsers should
>duck this issue. The parsing mechanism is quite easy to implement.
While these are nice to have, they are not entirely needed. Much the
same effect can be achieved using different stylesheets. In one
stylesheet, one can say "any text enclosed by this element should be
hidden" and in another, one can say "any text enclosed by this element
should be rendered in italics".
This mechanism could suffice for things like expert and amateur
differentitation, but could fail for mixed languages etc.