Incidentally, while we're talking about the draft, I have a suggestion.
I'd like to split the draft in two. It actually contains two types of
information -- what people are doing experimentally and what folks consider
standard ("ought to have in your implementation").
I'd prefer to see two drafts -- one which is "here's the standard package"
and "here's research you might want to know about". Otherwise we'll
have vendors and users quibbling over what in the document does and does
not have to be implemented...
Craig
This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:31 EST