Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: XHTML2.0

From: David Dorward <dorward@-----.--->
To: NULL
Date: 2/5/2006 11:01:00 PM
guitar.is.good@g... wrote:

> I have done a fair bit of personal web design in XHTML 1.0/1.1 strict

Quite useful for authoring content in, but not all that suitable for use on
the WWW (the handwaving of Appendix C for XHTML 1.0 is silly at best (and
depends on bugs in HTML 4 user agents), and doesn't apply to 1.1 at all)

> and am very curious about XHTML2.0.

> To my understanding it is still in draft, but is it actually in use?

I seem to recall one person experimenting with it and transforming it with
client side XSLT. It really is not something you should be using on the WWW
at the moment.

> Ultimately I want to design a simple XHTML2.0 webpage for a LAN running
> on the current apache2 webserver.  But I can not figure out how to code
> an XHTML2.0 page.

XHTML 2.0 is still subject to change. It isn't supported, AFAIK, by any user
agent except as generic XML.

> The actual content seems fairly standard, but the 
> doctypes etc I can not get to validate on the w3c validator.

From the latest draft:

     This version includes an early implementation of XHTML 2.0 in RELAX NG
     [RELAXNG], but does not include the implementations in DTD or XML
     Schema form. 

So any DTD you might find is out of date.

> It especially gives my gumpf about mime types, but I dont know haw to
> solve it (I read xhtml2.0 needs an special xml type mime type)

I believe that you use the regular XHTML content type, with a parameter
specifying a version. I don't think the syntax of that parameter has been
defined yet (other then being in the standard form for HTTP).

> Is it feasable to code a website in XHTML2.0

No.

> , ignoring compatability issues (I heard mozilla firefox is the only
> browser compatible

I'm pretty sure it isn't.

> Something I really like the look of in XHTML2.0 is the section + h
> elements and the ability to put link / href attributes in any element,
> makes much more sense!

It is nice syntax for authoring, client support is absent at present. Treat
some draft of XHTML 2.0 (or a subset of same) as a custom XML format. Write
your own schema. Transform it to HTML 4.01 before serving to to clients.

-- 
David Dorward       <http://blog.dorward.me.uk/>   <http://dorward.me.uk/>
                     Home is where the ~/.bashrc is


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent