<?xml version='1.0'?>

<reference anchor='RFC2295'>

<front>
<title abbrev='HTTP Content Negotiation'>Transparent Content Negotiation in HTTP</title>
<author initials='K.' surname='Holtman' fullname='Koen Holtman'>
<organization>Technische Universiteit Eindhoven</organization>
<address>
<postal>
<street>Postbus 513</street>
<street>Kamer HG 6.57</street>
<street>5600 MB Eindhoven (The Netherlands)</street></postal>
<email>koen@win.tue.nl</email></address></author>
<author initials='A.H.' surname='Mutz' fullname='Andrew H. Mutz'>
<organization>Hewlett-Packard Company</organization>
<address>
<postal>
<street>1501 Page Mill Road 3U-3</street>
<street>Palo Alto CA 94304</street>
<country>USA</country></postal>
<facsimile>+1 415 857 4691</facsimile>
<email>mutz@hpl.hp.com</email></address></author>
<date month='March' year='1998' />
<area>Applications</area>
<keyword>HTTP</keyword>
<keyword>hypertext transfer protocol</keyword>
<abstract>
<t>
   HTTP allows web site authors to put multiple versions of the same
   information under a single URL.  Transparent content negotiation is
   an extensible negotiation mechanism, layered on top of HTTP, for
   automatically selecting the best version when the URL is accessed.
   This enables the smooth deployment of new web data formats and markup
   tags.
</t></abstract></front>

<seriesInfo name='RFC' value='2295' />
<format type='HTML' octets='149229' target='http://xml.resource.org/public/rfc/html/rfc2295.html' />
<format type='XML' octets='126920' target='http://xml.resource.org/public/rfc/xml/rfc2295.xml' />
</reference>
