RE: Token question

Although this is not the right place for this I'll just be quick on sharing
my thoughts.

Although SGML may say what it says comments should be dropped -and it's
right, because someone can think of them as of not directly relevant info,
while my guess is the spec says so just to keep comments to (be used
as/become) something else- my personal opinion says that authors should have
the option to preserve them if they think they are really useful to them or
to the next document user.
Oh well, there may not be a perfect answer. OR, maybe the choice of keeping
comments should always be on the document receiver instead. 

Cheers,
Manos

PS: I haven't seen any other parts of the thread.

-----Original Message-----
From: Jan Roland Eriksson [mailto:jrexon@newsguy.com]
Sent: Saturday, March 03, 2001 1:25 PM
To: www-style@w3.org
Subject: Re: Token question


On Fri, 02 Mar 2001 17:41:49 +0100, glazman@netscape.com (Daniel
Glazman) wrote:

>Peter S. Linss wrote:
>> And to answer the original question, no, the browser should not have
>> ignored the CSS, it is perfectly valid.

>This brings to my mind a DOM issue related to comments : they are not
>preserved by DOM level 2, which is a terrible thing from an author's
>perspective.

Care to elaborate a bit on why excluding comments from the parse tree
would be bad for authors?

As I see it, a comment "lives" in the source only, as means for authors
to include "commentary only" info in the source.

It should be noted that SGML says that comments in markup can never
contain normative information and that they shall be dropped in the
parsing process, and if so, a source code comment can not/shall not be
used for anything but "stating notes in a source".

I'd like to think that such a view should be extended to cover all types
of "comments" in sources where ever they occur. Right,Wrong?

-- 
Jan Roland Eriksson <rex@css.nu> .. <URL:http://css.nu/>

Received on Saturday, 3 March 2001 06:37:30 UTC