Surely if the purpose is of the RFC is to provide
a similar facility to HTML, and it in fact provides a completely
different one, it indicates either that an interpretation is
wrong or that the wording is buggy?
You don't want the case where the RFC could have
said its purpose was to provide a *dissimilar* facility to
HTML with the exactly same level of truth...
Rick