W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > April 2008

RE: unescape-markup - support for text/xml

From: <Toman_Vojtech@emc.com>
Date: Mon, 28 Apr 2008 04:52:59 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870AD520DE@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-wg@w3.org>

> > Section 7.1.25 (p:unescape markup) says:
> > 
> > "All implementations must support the content type 
> > application/xml, and
> > must use a standard XML parser for it. It is a dynamic error
> > (err:XC0051) if the content-type specified is not supported by the
> > implementation."
> > 
> > Shouldn't the implementations be required to support also 
> text/xml and
> > not only application/xml?
> > 
> 
> Three more questions:
> 
> 1. Shouldn't it be an error if the document element contains anything
> else than text content?
> 2. What error should be reported if the unescaped content does not
> represent well-formed XML or cannot be parsed?
> 3. What should happen if the document element already specifies a
> default namespace and the 'namespace' option is provided on
> p:unescape-markup?
> 

One more remark:

I think that the sentence: 

"The octet-stream that results from decoding the text must be
interpreted using the specified encoding to produce a sequence of
Unicode characters to parse."

Should read:

"The octet-stream that results from decoding the text must be
interpreted using the specified CHARSET to produce a sequence of Unicode
characters to parse."

Regards
Vojtech
Received on Monday, 28 April 2008 08:54:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 28 April 2008 08:54:10 GMT