Re: Finishing the XML-tagging discussion

["Marshall Rose" <mrose+mtr.netnews@xxxxxxxxxxxxxxxx>]

> > > One alternative - not necessarily one I am advocating, but just
listing for
> > > completeness - is to use a similar approach but swapped round:
> > >
> > > image/svg;ContentLanguage=xml
>
> > I favor something like this.  it seems like it will interact more
> > cleanly with content negotiation mechanisms (as opposed to those
> > mechanisms having to acquire new pattern-matching facilities)
>
> > it's true that as MIME is architected the parameter space is on a
> > per-content-type basis.  but I don't see any great harm if we define
> > some global parameter name space (say, parameter names that begin
> > with "$" are global).  Then we could do something like:
>
> > content-type: image/svg; $superclass="application/xml"

ned - i agree with your take that having global parameters is a major change
to MIME.

suppose we were just to have something like:

    Content-type: image/svg; representation="xml"

where "representation" is just a plain old MIME parameter.

would you object to something along these lines?

/mtr