> This is a one-way hashing algorithm. Will always be 32 base-64 encoded
> chars long. ie:
> MD5("foobar") = 3858f62230ac3c915f300c664312c63f
Where does a user get a standalone base64 binary that will hash a string
argument so the result can be included?
> This is to make sure that the referenced document has not changed since
> the author made the link.
This obviously refers to some mechanism that I'm not familiar with. Where
in the referenced doc will the matching string appear? Or is this something
that a MIME-compliant system generates (by the goddess my MIME knowledge is
_not_ up to scratch :-)
> > l. Does nowrap in <p> effectively imply auto-<br>?
>
> God I hope not. I read it to mean that <p nowrap> is basically a <pre>
> segment not in a monospaced font.
I'm sorry...I didn't mean it like that. I meant what you say: <p nowrap>
means "honor my linebreaks please".
> > r. Where is this RANGE control implemented? Is SIZE="1,10" meant to
> > imply limits:min=1,max=10 ?
>
> Emacs-w3 implements it. SIZE="1,10" implies min=1, max=10. Personally,
> I would like to see that broken out into <input type=range min=1 max=10>
OK, so there's not a RANGE attribute...the caps had me fooled. I agree with
type=range though, altho why did we ditch type=number?
> What happened to the 'named' base tags from the HTML 3.0 spec that was
> distributed at the IETF meetings in San Jose? I thought it was very
> useful, and it was trivial to implement.
Whoops, I must have missed that one while I was away.
> > x. Do we have real-life examples of META yet?
>
> Other than netscape, no. Emacs-w3 stores them, but doesn't do anything
> yet.
Are those buried in Netscapes online documentation?
> Good points all, peter, but couldn't you have thought of one more to get
> all the way through the alphabet? :)
z. We need to expand the explanatory text :-)
///Peter