- From: Larry Masinter <masinter@parc.xerox.com>
- Date: Wed, 6 Sep 1995 18:09:28 PDT
- To: brian@organic.com
- Cc: koen@win.tue.nl, fielding@beach.w3.org, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, koen@win.tue.nl
The number of attributes a server *could* send for a particular document is nearly infinite; images could be selected on size and pixel depth; audio streams on compression methods, data rate or bits per sample; postscript files on version, use of color, etc. 406 responses might be able to characterize these when the service doesn't perform any conversion, but 'accept' style negotiation works better in other circumstances. Let me suggest again "accept-parameter: <parameter><rel><value>" where <parameter> is a parameter to a number of media types (e.g., charset), <rel> is a relation operator (e.g., =), and <value> is a value specifier consistent with <rel>. This will apply 'to all accepted media types for which the parameter applies', and the q value operates by modifying the q of the original media type. (If revisedq = f(mediaq, parameterq), I'm not sure what f should be, but I think 'product', e.g., revisedq=mediaq * parameterq.
Received on Wednesday, 6 September 1995 18:15:56 UTC