James M Snell wrote: > Brian Smith wrote: > > Can atom:link/@type and atom:content/@type reference media > > types with parameters like "application/atom+xml;type=entry"? > > If so, what is the syntax supposed to be? > > Of course. The syntax is nothing special: > > <link type="application/atom+xml;type=entry" href="..." /> > > Quoted parameters will need to be escaped of course... > > <link type="application/atom+xml;type="entry"" > href="..." />
I understand the general syntax. However, the details are what I am unsure about. : 1. What leading/trailing/internal whitespace is allowed? (Right now I allow all this whitespace, just as RFC 2616 does for Content-Type.) 2. What characters are allowed in a parameter value? (Currently, I do as RFC 2616 does.) 3. What escaping mechanism is used for quoted parameter values? For example, how would one represent a parameter value containing a '"'? (Currently, I use the backslash as the escape character like RFC 2616 does.) 4. How do you handle codepoints above \u007f and especually above \u00ff in parameter values? Right now I allow only characters that are in ISO-5591-1. 5. Should we really restrict parameter names to RFC 4288 reg-name? (Right now, I use the RFC 2616 token production, which is more general.) I have a validator in my software which accepts every valid entry and rejects every invalid entry. It already handles all these edge caes but I would like to know if anybody disagrees with any of the decisions I have made. Thanks, Brian
