I am not comfortable referencing documents (in an IETF message) that
are available only via the system in which I'm trying to document.
I.e. for the purpose of conveying to the IETF what all we're up to
it would be best to have files in the anonymous FTP area and rendered
Calling HTML an "SGML application" is not a bad long term plan. I
fear there's some risk in ease of implementation from
Content-type: text/sgml; dtd="(string that identifies html.dtd)"
and as such I'd prefer to not haul in all of the SGML standard in the
description of the system, not right up front at least. Better to
spec something that you can deliver and play with rather than stretch
things out to their limits.
is in fact something that should get a "public text identifier" (some
kind of ISBN number?) then we should do it. That would be a very
useful document to reference in the comments section.
Edward Vielmetti, vice president for research, Msen Inc. emv@Msen.com
Msen Inc., 628 Brooks, Ann Arbor MI 48103 +1 313 998 GLOB