- From: Keith Moore <moore@cs.utk.edu>
- Date: Sun, 26 Oct 1997 16:57:59 -0500
- To: michaelm@rwhois.net
- cc: moore@cs.utk.edu (Keith Moore), masinter@parc.xerox.com, Harald.T.Alvestrand@uninett.no, asgilman@access.digex.net, connolly@w3.org, timbl@w3.org, fielding@ics.uci.edu, uri@bunyip.com, lassila@w3.org, swick@w3.org, tbray@textuality.com, jeanpa@microsoft.com, cmsmcq@uic.edu, dsr@w3.org, lehors@w3.org, ij@w3.org
> I think Dan's other suggestion was: > > d) let the IETF define those things and then let the W3C cite > those RFCs it thinks are appropriate to what the W3C wants to do. URL and URN are already defined. If Dan wants to write up a document defining URI and ask IETF to publish it as an RFC, he's welcome to do so. But even under ideal circumstances, this will take at least a month...perhaps much longer. My personal opinion is that it's not worth a month or more's delay to define a new term in an RFC, when the HTML spec can be made reasonably clear and precise without doing so. Will the delay have any tangible benefits for the end-user? Being on the IESG has made me sensitive to delays...it's amazing how many documents sit around for weeks or months for reasons that have nothing to do with either the technical description of the protocol or the recommendations for use of that protocol. So my mantra has become "get things out the door so people can use them" Keith
Received on Sunday, 26 October 1997 16:58:22 UTC