XHTML2 versus HTML5 - Revision history

Annevk at 15:45, 10 November 2012

2012-11-10T15:45:17Z

← Older revision		Revision as of 15:45, 10 November 2012
Line 1:		Line 1:
	{{obsolete}		{{obsolete}}

	http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123/		http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123/

Annevk: Film at 11

2012-11-10T15:45:05Z

Film at 11

← Older revision		Revision as of 15:45, 10 November 2012
Line 1:		Line 1:
			{{obsolete}

	http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123/		http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123/

TheresaOConnor: Reverted edits by RBorja97 (talk) to last revision by Dean

2011-10-10T20:15:50Z

Reverted edits by RBorja97 (talk) to last revision by Dean

← Older revision		Revision as of 20:15, 10 October 2011
Line 28:		Line 28:
	=== The blockcode element ===		=== The blockcode element ===

	HTML5 does not have this element. In HTML5 you can use <pre><code> instead.		HTML5 does not have this element. In HTML5 you can use <pre><code> instead.

	'''Rationale:''' the blockcode element is not backwards compatible.		'''Rationale:''' the blockcode element is not backwards compatible.
Line 36:		Line 36:
	HTML5 does not have the h element. In HTML5 the h1-h6 elements work together with the section element. In XHTML2 only the h element works with the section element.		HTML5 does not have the h element. In HTML5 the h1-h6 elements work together with the section element. In XHTML2 only the h element works with the section element.

	'''Rationale:''' the h element is not backwards compatible. Also, it seems important to define interaction between the h1-h6 elements and <span class="plainlinks">[http://thoughtmechanics.com/ <span style="color:black;font-weight:normal;text-decoration:none!important;background:none!important; text-decoration:none;">web design service in atlanta</span>]</span> the section element so authors can more easily reuse existing content and assistive technology can still make sense of invalid pages.		'''Rationale:''' the h element is not backwards compatible. Also, it seems important to define interaction between the h1-h6 elements and the section element so authors can more easily reuse existing content and assistive technology can still make sense of invalid pages.

	=== The separator element ===		=== The separator element ===

RBorja97: None

2011-10-10T09:32:13Z

None

← Older revision		Revision as of 09:32, 10 October 2011
Line 28:		Line 28:
	=== The blockcode element ===		=== The blockcode element ===

	HTML5 does not have this element. In HTML5 you can use ~~<~~pre>~~<~~code> instead.		HTML5 does not have this element. In HTML5 you can use <pre><code> instead.

	'''Rationale:''' the blockcode element is not backwards compatible.		'''Rationale:''' the blockcode element is not backwards compatible.
Line 36:		Line 36:
	HTML5 does not have the h element. In HTML5 the h1-h6 elements work together with the section element. In XHTML2 only the h element works with the section element.		HTML5 does not have the h element. In HTML5 the h1-h6 elements work together with the section element. In XHTML2 only the h element works with the section element.

	'''Rationale:''' the h element is not backwards compatible. Also, it seems important to define interaction between the h1-h6 elements and the section element so authors can more easily reuse existing content and assistive technology can still make sense of invalid pages.		'''Rationale:''' the h element is not backwards compatible. Also, it seems important to define interaction between the h1-h6 elements and <span class="plainlinks">[http://thoughtmechanics.com/ <span style="color:black;font-weight:normal;text-decoration:none!important;background:none!important; text-decoration:none;">web design service in atlanta</span>]</span> the section element so authors can more easily reuse existing content and assistive technology can still make sense of invalid pages.

	=== The separator element ===		=== The separator element ===

Dean: ...whereas `xml:id` can only be used in XML documents.

2009-01-25T09:39:03Z

...whereas <code>xml:id</code> can only be used in XML documents.

← Older revision		Revision as of 09:39, 25 January 2009
Line 82:		Line 82:
	=== The xml:id attribute ===		=== The xml:id attribute ===

	HTML5 does not have this attribute, however, xml:id can be used in XHTML5 web pages		HTML5 does not have this attribute, however, <code>xml:id</code> can be used in XHTML5 web pages.

	'''Rationale:''' there already is an id attribute that works fine and can be used both in HTML and XHTML web pages.		'''Rationale:''' there already is an id attribute that works fine and can be used both in HTML and XHTML web pages whereas <code>xml:id</code> can only be used in XML documents.

	=== The layout attribute ===		=== The layout attribute ===

Dean: however, xml:id can be used in XHTML5 web pages

2009-01-25T09:35:27Z

however, xml:id can be used in XHTML5 web pages

← Older revision		Revision as of 09:35, 25 January 2009
Line 82:		Line 82:
	=== The xml:id attribute ===		=== The xml:id attribute ===

	HTML5 does not have this attribute.		HTML5 does not have this attribute, however, xml:id can be used in XHTML5 web pages

	'''Rationale:''' there already is an id attribute that works fine.		'''Rationale:''' there already is an id attribute that works fine and can be used both in HTML and XHTML web pages.

	=== The layout attribute ===		=== The layout attribute ===

Annevk: remove unneeded remark

2009-01-24T14:31:57Z

remove unneeded remark

← Older revision		Revision as of 14:31, 24 January 2009
Line 1:		Line 1:
	http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123/		http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123/

	This is not a HTML vs XHTML ~~article~~, instead this page is an attempt to find out where XHTML2 and HTML5 features overlap, why certain design decisions in HTML5 have been made different, and why HTML5 lacks certain features XHTML2 has.		This is not about HTML versus XHTML, instead this page is an attempt to find out where XHTML2 and HTML5 features overlap, why certain design decisions in HTML5 have been made different, and why HTML5 lacks certain features XHTML2 has.

	It is not an attempt to demonstrate that 5 > 2. We know that ~~(we are just waiting for the W3C to admit it)~~.		It is not an attempt to demonstrate that 5 > 2. We know that.

	It is also very simple at this point. I wish my time was infinite.		It is also very simple at this point. I wish my time was infinite.

Dean: removed my last edit and merged ideas into the first sentence that anne wrote

2009-01-24T13:57:38Z

removed my last edit and merged ideas into the first sentence that anne wrote

← Older revision		Revision as of 13:57, 24 January 2009
Line 1:		Line 1:
	http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123/		http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123/

	This page is an attempt to find out where XHTML2 and HTML5 features overlap, why certain design decisions in HTML5 have been made different, and why HTML5 lacks certain features XHTML2 has.		This is not a HTML vs XHTML article, instead this page is an attempt to find out where XHTML2 and HTML5 features overlap, why certain design decisions in HTML5 have been made different, and why HTML5 lacks certain features XHTML2 has.

	It is not an attempt to demonstrate that 5 > 2. We know that (we are just waiting for the W3C to admit it).		It is not an attempt to demonstrate that 5 > 2. We know that (we are just waiting for the W3C to admit it).

	~~This article is not about HTML vs XHTML, it is about comparing the proposed features of XHTML2 to the features of (X)HTML5.~~

	It is also very simple at this point. I wish my time was infinite.		It is also very simple at this point. I wish my time was infinite.

Dean: added: This article is not about HTML vs XHTML...

2009-01-24T13:49:44Z

added: This article is not about HTML vs XHTML...

← Older revision		Revision as of 13:49, 24 January 2009
Line 4:		Line 4:

	It is not an attempt to demonstrate that 5 > 2. We know that (we are just waiting for the W3C to admit it).		It is not an attempt to demonstrate that 5 > 2. We know that (we are just waiting for the W3C to admit it).

			This article is not about HTML vs XHTML, it is about comparing the proposed features of XHTML2 to the features of (X)HTML5.

	It is also very simple at this point. I wish my time was infinite.		It is also very simple at this point. I wish my time was infinite.

Dean: a cheeky reminder about web politics

2009-01-24T13:43:07Z

a cheeky reminder about web politics

← Older revision		Revision as of 13:43, 24 January 2009
Line 3:		Line 3:
	This page is an attempt to find out where XHTML2 and HTML5 features overlap, why certain design decisions in HTML5 have been made different, and why HTML5 lacks certain features XHTML2 has.		This page is an attempt to find out where XHTML2 and HTML5 features overlap, why certain design decisions in HTML5 have been made different, and why HTML5 lacks certain features XHTML2 has.

	It is not an attempt to demonstrate that 5 > 2. We know that.		It is not an attempt to demonstrate that 5 > 2. We know that (we are just waiting for the W3C to admit it).

	It is also very simple at this point. I wish my time was infinite.		It is also very simple at this point. I wish my time was infinite.