marked sections (was navigability)

• Mail folder: WWW Talk Apr 94-present
• Next message: Gavin Nicol: "Re: The value of navigability (related to META...)"
• Previous message: Vinay Kumar: "Re: SECURITY ALERT! [Re: How do you execute shell scripts in Mosaic]"

Errors-To: listmaster@www0.cern.ch
Date: Tue, 7 Jun 1994 18:44:20 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <0097F9B4.13836B94.46@vax.ox.ac.uk>
Errors-To: listmaster@www0.cern.ch
Reply-To: lou@vax.ox.ac.uk
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Lou Burnard <lou@vax.ox.ac.uk>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: marked sections (was navigability)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas

Dave Raggett wrote:

>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
..

to which GTN wrote:

>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".

But this would require you to define a structure in which ALL of the
elements you might possibly want to switch on/off can coexist. This is
simply not possible for many real documents.

Marked sections are a boon because they allow you to encode alternatives
which you know cannot co-exist in the same document structure.

LB