OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Media Type parameters


Section 3.3 of WD11 defines a set of media type parameters that can  
be used to further specify a media type.

When a proxy resolver receives these media type parameters in a URI  
query string, as opposed to an Accept header, the issue arises that  
the semicolon is recommended by the W3C as an alternative field  
separator in query strings <http://www.w3.org/TR/1999/REC- 
html401-19991224/appendix/notes.html#h-B.2.2>, and most  
implementations seem to work this way (verified in PHP and Ruby on  
Rails).

So for example, when parsing the query string in the following URI:
http://xri.net/=drummond?_xrd_r=application/xrds 
+xml;sep=true;nodefault=type&_xrd_t=http://openid.net/signon/1.1

rather than an "_xrd_t" field and an "_xrd_r" field with two  
parameters attached, four distinct field-value pairs will be returned:

_xrd_r=application/xrds xml
sep=true
nodefault=type
_xrd_t=http://openid.net/signon/1.1

I'd suggest therefore that a set of more distinct names be defined  
for media type parameters when used in a query string, something like  
"_xrd_r_nodefault" instead of "nodefault".

=vg


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]