Oh dear! I've made all the changes that Misha has so brilliantly
explained (as if he's been practicing with small children), with
one exception. What exception do you ask? Here is that exception. ;-)
> Date: Wed, 04 Feb 1998 17:03:21 +0000 (GMT)
> From: Misha Wolf <[log in to unmask]>
> ...
> > 3.9. Format Label: "Format"
> >
> > The data format of the resource, used to identify the software
> > and possibly hardware that might be needed to display or operate
> > the resource. For the sake of interoperability, Format should be
> > selected from an enumerated list that is currently under development
> > in the workshop series.
>
> Charles suggests the word "on" between "operate" and "the resource".
The word "on" wouldn't be appropriate (unless the resource were gravely
ill) because the word "operate" is meant as a general form of the word
"execute", as in, "to execute a program". To have used the word "execute"
instead might appear to exclude physical (ie, non-electronic) resources
that are meant to be "operated", as in, "to operate a machine".
It was a bit of inspired generalization, but if "operate" is too confusing
would "execute" work better?
> Finally, Charles suggests that all TABs be replaced with the appropriate
> numbers of SPACEs, as the rendering of TABs is device dependent. The
> relevant RFC [1] doesn't actually forbid TABs, but it does not use them
> itself.
>
> [1] "Instructions to RFC Authors", http://ds.internic.net/rfc/rfc2223.txt
I haven't re-read this in a while, but I did go ahead and expand tabs
to spaces.
Thanks for the comments.
-John
|