[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] Type and Media parameters
Funny enough, RFC 4229 [1] was just published this week, which defines the initial contents of the HTTP header registry, which itself is defined in RFC 3864 [2]. This is just registration (which is way down the road for us, if ever).. -Gabe [1] http://www.rfc-editor.org/rfc/rfc4229.txt or [2] http://www.rfc-editor.org/rfc/rfc3864.txt > -----Original Message----- > From: Tan, William [mailto:William.Tan@neustar.biz] > Sent: Wednesday, December 28, 2005 11:53 PM > To: Victor Grey; xri@lists.oasis-open.org > Subject: RE: [xri] Type and Media parameters > > I'm nervous about using Pragma, and the fear may not be > founded. RFC2616 > says that "All pragma directives specify optional behavior from the > viewpoint of the protocol", but we are using it to specify at least > SHOULD level behavior. > > Also, there is widespread legacy implementation interpreting > the Pragma > header which could potentially cause problems. > > I'm not sure what is required to define new HTTP headers, but I'm in > favor of using a new X-XRI-ServiceType header. > > Wil. > > > -----Original Message----- > > From: Victor Grey [mailto:victor@idcommons.org] > > Sent: Wednesday, December 28, 2005 12:08 PM > > To: xri@lists.oasis-open.org > > Subject: [xri] Type and Media parameters > > > > 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_med > iatype=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 > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this mail list, you must leave the OASIS TC that > > generates this mail. You may a link to this group and all > your TCs in > > OASIS > > at: > > > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all > your TCs in OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr > oups.php > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]