Re: well-formedness error

[Julian Reschke <julian.reschke@xxxxxx>]

Asbjørn,

you have made your point clear why you don't think that just mandating 
an "application/*" MIME type will be enough (I think that argument is 
lame because it basically says that no new content types can be 
introduced in practice, but anway...).

Do you have a specific proposal what to do *instead*?

For the sake of completeness:

> > > > As long as it isn't text/*, that's fine.
> > >
> > > And then you're stuck with US-ASCII, no matter what the characters in  the  XML is encoded with, and no matter what you state in the  processing  instruction. Which means that statically served web pages  can _only_ be in  english, and never include terms or words from other  languages.
> >
> >
> > Again, that's incorrect. It would really be good if you re-read RFC3023  before making these claims.
>
>
> I'm claiming that 'text/*' binds you to US-ASCII. Is that incorrect? 

- text/* with no encoding declaration binds you to US-ASCII. Others 
(such as application/*) don't.

- being bound to US-ASCII doesn't mean you can't use non-ASCII 
characters; you just need to properly escape them, btw

- nit: it's not the "processing instruction", it's the "XML declaration".


Julian