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="..." />
- James
Currently, I am using RFC 2616's media-type syntax so that these attributes
have a syntax consistent with HTTP Content-Type headers, and because RFC
5023 already re-uses the RFC 2616 media-range syntax. Is anybody handling it
any other way?
RFC 4287 references RFC 4288 for the syntax of atom:link/@type and
atom:content/@type. However, RFC 4288 doesn't define a syntax for media
types with parameters. I suppose we are supposed to use something similar to
what RFC 2045 and RFC 2616 use, but each of those have different grammars
for this construct. The parts of the syntax that RFC 4288 *does* define are
more restrictive than the syntax used by RFC 2616, but RFC 4288's
constraints are for registered MIME types, not all MIME types.
Regards,
Brian
