Re: unescaping markup

/ Alex Milowski <alex@milowski.org> was heard to say:
| 2) What are the appropriate content types to use for other types of
|> documents to trigger vs. not trigger this behavior?
|
| Using media types allows vendors to specify content handling behavior
| using specialized media types or  unregistered types (e.g.
| "application/x-goop"
| or "application/vnd-random-stuff")

So the content-type tells me the type that I should expect to get when I
unwrap the escaped markup. So, told to expect text/html, I know that I
will have to run tagsoup or some similar component to turn it into well
formed XML.

What would a content-type of "application/vnd-random-stuff" tell me?
That instead of running tagsoup I should run some other cleanup process?

Can I (as an implementor) assert that I accept "image/png" as a
content-type and that my cleanup process is to base64 encode the data
and wrap it in an <image> tag? Am I allowed (or required?) to fail if
the data isn't a PNG image?

If I see a content-type I don't recognize, can I try running tagsoup or
must I fail?

This all seems to expose complexity and interoperability issues that
don't have much obvious value.

Are there any actual use cases for content-types other than
application/xml (or application/*+xml) and text/html?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | What are the thoughts of the canvas on
http://nwalsh.com/            | which a masterpiece is being created?
                              | "I am being soiled, brutally treated
                              | and concealed from view." Thus men
                              | grumble at their destiny, however
                              | fair.--Jean Cocteau