Re: XHTML as XML

Lachlan Hunt wrote:

Google does not support XHTML served as XML.  Although it will still 
index the documents, it will simply state "File Format Unrecognised" 
within search results.

---------------------------------------


I consider the above statement for not relevant. I have been serving
XHTML 1.1 as xml to Google for almost two months now, and Google is in
love with my web pages. Hundreds of people are arriving to my website
from Google every day. I keep track of each visitor, and log the search
terms they are using.

It is probably only a matter of time before Google announces or let it
be known that web pages served as xml get higher ranking. At least
Google should be in favor of quality web pages and help promote a more
semantic web.

Best regards,
Jesper Tverskov

Please note:
The discussion about background-color and the body and html element has
by some mistake been transferred to the CSS-list where it also belongs.


-----Oprindelig meddelelse-----
Fra: Lachlan Hunt [mailto:lachlan.hunt@iinet.net.au] 
Sendt: 9. februar 2005 07:05
Til: Jesper Tverskov
Cc: www-html@w3.org
Emne: Re: XHTML as XML

Jesper Tverskov wrote:
> 1) What would you consider Best Practice to use as mime-type for user
> agents, web spiders, etc., not sending an HTTP accept-header?

Assume text/html, unless told otherwise.

> I have decided to give them the best I have to offer,
> application/xhtml+xml. I have two arguments. A) Since they don't send
an
> http accept-header they either don't need to know about mime-types in
> order to work or they are not worth dealing with. B) Google is not
> sending an accept-header, and I would like Google to be able to detect
> that I offer my XHTML as XML.

Google does not support XHTML served as XML.  Although it will still 
index the documents, it will simply state "File Format Unrecognised" 
within search results.

> 2) Is it a bug for Mozilla/FireFox suddenly to require that we also
> style the html element with background-color similar to the body
> element?

No, it's not a bug.  It's simply the way rendering real XHTML works. 
That is described within the Mozilla FAQ document you linked to, but in 
the following question [1]:
| # CSS works according to the XML+CSS rules.
|   * HTML-specific CSS exceptions do not apply. For example, the body
|     element gets no special treatment.

[2] http://www.mozilla.org/docs/web-developer/faq.html#xhtmldiff

-- 
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/    Rediscover the Web
http://SpreadFirefox.com/   Igniting the Web

Received on Thursday, 10 February 2005 10:20:10 UTC