Now I am even more confused!  
I was always under the impression that HTML4 and lower were valid SGML.
That XHTML1 and up were valid XML
That XML was valid SGML

So how the ??? does that leave us with either 'serialisation' of the new
language being in-compatible with SGML?

Regards,
Mike

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of David Dorward
Sent: 26 November 2008 11:07
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] HTML/XHTML/XML - Question about the future of.

[EMAIL PROTECTED] wrote:
> Why do you say that HTML5 will not be valid SGML? 

I didn't. I said it wouldn't be SGML. The syntax might (I haven't looked
closely enough at it to determine) be valid within the rules of SGML. I
don't think it can be parsed as SGML though.

"Because SGML has never been deployed in browsers and many html
authoring tools, HTML 5 defines a new serialization called html, which
looks a lot like the previous known SGML."

  -- http://www.w3.org/QA/2008/01/html5-is-html-and-xml.html

"For compatibility with existing content and prior specifications, this
specification describes two authoring formats: one based on XML
(referred to as XHTML5), and one using a custom format inspired by SGML"

  -- http://www.w3.org/html/wg/html5/

"While the HTML form of HTML5 bears a close resemblance to SGML and XML,
it is a separate language with its own parsing rules."

  -- http://www.w3.org/TR/html5/parsing.html

-- 
David Dorward                               <http://dorward.me.uk/>


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************



*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to