One question about these predefined symbols, <URL:http://www.w3.org/pub/WWW/TR/WD-wwwicn>: Both &binhex.document; and &uuencoded.document; are defined. Is there a reason not to have a more general description, like &encoded.document;? I can see at least one pro and con: Con: Lazy authors, or those who didn't know any better, might use &encoded.document; without telling the reader how it was encoded. Also automatic directory indexing software might not be as informative. Pro: More general, if another encoding mechanism becomes popular, another entity doesn't have to be added. Also, if a suitable name was chosen, couldn't encrypted documents be described by this entity as well? -- JosephReceived on Friday, 12 January 1996 11:45:57 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:38:38 GMT