[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Well-formedness statistics

This doesn't seem very consistent to me. On the one hand taking the MIME type seriously enough that encoding mismatches are called well-formedness errors but on the other ignoring it and resorting to content sniffing if the MIME type isn't an XML MIME type. Despite that, the stats you provided are still useful. Thanks for taking the time to do it.  
 
RE http://www.25hoursaday.com/rss10.xml <http://www.25hoursaday.com/rss10.xml> 
 
That isn't my feed. My feed is http://www.25hoursaday.com/weblog/SyndicationService.asmx/GetRss  
 
-- 
PITHY WORDS OF WISDOM
There are always two solutions to the problem: yours and the boss's. 

________________________________

From: Mark Pilgrim [mailto:pilgrim@xxxxxxxxx]
Sent: Wed 6/23/2004 8:11 AM
To: Dare Obasanjo
Cc: atom-syntax@xxxxxxx
Subject: Re: Well-formedness statistics



On Wed, 23 Jun 2004 06:59:08 -0700, Dare Obasanjo <dareo@xxxxxxxxxxxxx> wrote:
> So you count a document served as text/plain as well-formed XML?

I can find nothing in the XML specification stating that XML documents
MUST NOT be served as text/plain.  I can find nothing in RFC 3023
stating that XML documents MUST NOT be served as text/plain.  RFC 2046
states that "us-ascii" is the default character encoding for all
"text/*" content types.  RFC 2646 updates 2046 but does nothing to
change the default character encoding.

Therefore, if an XML document
1. is served as "text/*",
2. does not specify a charset parameter in the HTTP Content-type, and
2. is parseable by a conformant XML parser using a "us-ascii" encoding
then I count it as well-formed.

This is the situation as best I understand it.  I would be happy if
someone could provide further clarification on how I should handle XML
served as "text/plain", "text/css", or "text/javascript".

Note that this does not affect the non-well-formedness of your feed at
http://www.25hoursaday.com/rss10.xml, which is served as "text/xml"
and therefore falls squarely under the jurisdiction of RFC 3023.

--
Cheers,
-Mark