<http://www.w3.org/TR/2001/NOTE-cuap-20010206> Excerpts: > *1.5* Allow the user to add new URI schemes in a straightforward way. > > For instance, allow users to associate external programs with URI > schemes. The user agent should inform the user when it does not > recognize a URI scheme in content. > > Example: > > A user may want the "tel" scheme (e.g., |tel:+33-4-12-34|) to > interact with their telephone. Or they may want the "irc" scheme > (e.g., |irc://irc.example.org/|) to activate an IRC client on > their desktop with a connection to the specified server. > (see <http://protozilla.mozdev.org>) > *3.1* Save resources retrieved from the Web on the local system using > the appropriate system naming conventions. > > Example: > > |http://www.w3.org/TR/1999/REC-html401-19991224/html40.ps| is a view > of the gzip'ed PostScript version of the HTML 4.01 specification. The > HTTP headers sent by the server include: > > Content-Type: application/postscript; qs=0.001 > Content-Encoding: gzip > > If saved locally, the filename on most computers should be > |html40.ps.gz| for the applications to recognize the file type. > > *Wrong:* Saving this compressed PostScript document as |html40.ps| is > likely to confuse other applications. > > *3.5* If a host name has multiple DNS entries, try them all before > concluding that the Web site is down. > > *3.6* List only supported media types in an HTTP |Accept| header. > > *Wrong:* User agent agents should not send an HTTP header of > |Accept: */*| since the server may support content types that the user > agent does not. For instance, if a server is configured so that SVG > images are preferred to PNG images, a user agent that only supports > PNG, GIF, and JPEG will receive (unsupported) SVG rather than > (supported) PNG. > -- This message is protected by ROT0 encryption and the DMCA. Reading is disallowed and will be prosecuted.
