Re: List of changes in Nov.7 draft from Sept. 17 version (fwd)

Rob (wlkngowl@unix.asb.com)
Mon, 17 Nov 1997 23:50:59 -0500


Message-Id: <199711181529.KAA05342@unix.asb.com>
From: "Rob" <wlkngowl@unix.asb.com>
To: Jordan Reiter <jreiter@mail.slc.edu>, www-html@w3.org
Date: Mon, 17 Nov 1997 23:50:59 -0500
In-reply-to: <l03110701b093b3b1324a@[192.168.1.128]>
Subject: Re: List of changes in Nov.7 draft from Sept. 17 version (fwd)

On 15 Nov 97, Jordan Reiter wrote:
> [..]
> My overall attitude is: INS and DEL, IMHO, are elements that although
> useful have an extremely limited range of behaviors. Revision is much more
> complicated than simple inserting and deleting. Sometimes you just have
> your downright overall change. But you still want to indicate a selection
> of text that has been changed. This is a problem. I currently see no way
> that INS and DEL can be correctly used because they degrade really ugily.
> [..]

There are two related needs here:

(1) the ability to note revisions in HTML (date/time, type of change, 
   reason and/or citation)
(2) markup related to revisions (INS/DEL or a proposed changed/updated 
   element).

(1) without any visible markup would be very useful by itself,
especially for situations where documents are maintained by more than
one person. The ability to have CSS pseudo-classes would enhance their
usefulness by explicitly highlighting revised portions of the document.

This can be added to the specification (perhaps as attributes to 
the DIV and SPAN elements) without any major problems. Even if there is 
no eventual support by browsers or even in the CSS spec, it would be a 
very useful feature to a lot of people. (Yes, one could always use 
comments, but standard attributes allow for automated use of them.)

Only with (2) is there an issue with degrading gracefully, specifically
with the DEL element. I can't think of a way around the problem.
However, INS and DEL are of limited use (mainly for legal documents
which might be better suited to a separate markup language rather than
HTML).  Whether this is resolved should not have any bearing on whether 
(1) is incorporated into the standard.

On a side note, a DATED element for marking dated sections of a document 
would be useful.

Rob








-----
"The word to 'kill' ain't dirty    | Robert Rothenburg wlkngowl@unix.asb.com
 I used it in the last line        | http://www.asb.com/usr/wlkngowl
 but use the short word for lovin' | http://www.wusb.org/mutant
 and Dad you wind up doin' time."  | PGP'd mail welcome (ID 0x5D3F2E99)