Type and Media parameters

[Victor Grey <victor@idcommons.org>]

As promised, here's my strawman proposal for a way for an xri resolver  
client to specify type and media parameters in a request.

The parameters can be specified in either a query string, url-encoded  
and  appended to the HXRI, or in the HTTP header (or both). If a type  
or media parameter is transmitted in both header and query string, the  
query string value will take precedence.

In the HTTP header, I propose that we use the Accept field for media  
type (which is fairly standard) and the Pragma field for the service  
type (here I am on more shaky ground. Based my choice on  
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.32  -  
comments solicited).

Examples---
In the HTTP header:
Accept: text/html
Pragma: xri_servicetype=xri://+contact*($v1.1)

Same thing in the query string:
xri_servicetype=xri%3A%2F%2F%2Bcontact%2A%28%24v1.1%29&xri_mediatype=tex 
t%2Fhtml
or for readability here it is before url-encoding:
xri_servicetype=xri://+contact*($v1.1)&xri_mediatype=text/html


If the HXRI contains an existing query string, the type and/or media  
parameters are appended to the existing query string with an "&".  
Otherwise the type and/or media parameters are appended to the path  
with an "?'. The order of the key/value pairs in a URI query string is  
not significant.

Regards,
=vg