HTML vs. XHTML - Revision history

Brettz9: /* Syntax and Parsing */

2011-08-21T12:41:12Z

Syntax and Parsing

← Older revision		Revision as of 12:41, 21 August 2011
Line 255:		Line 255:
	\| XML 1.0 only allows the following Unicode <code>#x9, #xA, #xD, [#x20-#xD7FF], [#xE000-#xFFFD], [#x10000-#x10FFFF]</code>		\| XML 1.0 only allows the following Unicode <code>#x9, #xA, #xD, [#x20-#xD7FF], [#xE000-#xFFFD], [#x10000-#x10FFFF]</code>

	XML 1.1 allows all Unicode (including all in 1.0) except for U+0000, U+FFFE, and U+FFFF (i.e., it allows <code>[#x1-#xFFFD] \| [#x10000-#x10FFFF]</code>)		XML 1.1 allows all Unicode (including all in 1.0) except for U+0000, U+FFFE, and U+FFFF (i.e., it allows <code>[#x1-#xFFFD], [#x10000-#x10FFFF]</code>)

	Both XML 1.0 and 1.1 discourage control-characters and non-characters:		Both XML 1.0 and 1.1 discourage control-characters and non-characters:

Brettz9: /* Syntax and Parsing */

2011-08-21T12:40:11Z

Syntax and Parsing

← Older revision		Revision as of 12:40, 21 August 2011
Line 258:		Line 258:

	Both XML 1.0 and 1.1 discourage control-characters and non-characters:		Both XML 1.0 and 1.1 discourage control-characters and non-characters:

	Discouraged in XML 1.0 only: <code>[#xFDE0-#xFDEF]</code> (spec typo?)		Discouraged in XML 1.0 only: <code>[#xFDE0-#xFDEF]</code> (spec typo?)

	Discouraged in XML 1.1 only (these are not allowed at all in 1.0): <code>[#x1-#x8], [#xB-#xC], [#xE-#x1F]</code>		Discouraged in XML 1.1 only (these are not allowed at all in 1.0): <code>[#x1-#x8], [#xB-#xC], [#xE-#x1F]</code>

	Discouraged in XML 1.0-1.1: <code>[#x7F-#x84], [#x86-#x9F], [#xFDD0-#xFDDF], [#x1FFFE-#x1FFFF], [#x2FFFE-#x2FFFF], [#x3FFFE-#x3FFFF], [#x4FFFE-#x4FFFF], [#x5FFFE-#x5FFFF], [#x6FFFE-#x6FFFF], [#x7FFFE-#x7FFFF], [#x8FFFE-#x8FFFF], [#x9FFFE-#x9FFFF], [#xAFFFE-#xAFFFF], [#xBFFFE-#xBFFFF], [#xCFFFE-#xCFFFF], [#xDFFFE-#xDFFFF], [#xEFFFE-#xEFFFF], [#xFFFFE-#xFFFFF], [#x10FFFE-#x10FFFF]</code>		Discouraged in XML 1.0-1.1: <code>[#x7F-#x84], [#x86-#x9F], [#xFDD0-#xFDDF], [#x1FFFE-#x1FFFF], [#x2FFFE-#x2FFFF], [#x3FFFE-#x3FFFF], [#x4FFFE-#x4FFFF], [#x5FFFE-#x5FFFF], [#x6FFFE-#x6FFFF], [#x7FFFE-#x7FFFF], [#x8FFFE-#x8FFFF], [#x9FFFE-#x9FFFF], [#xAFFFE-#xAFFFF], [#xBFFFE-#xBFFFF], [#xCFFFE-#xCFFFF], [#xDFFFE-#xDFFFF], [#xEFFFE-#xEFFFF], [#xFFFFE-#xFFFFF], [#x10FFFE-#x10FFFF]</code>
	\|		\|

Brettz9: /* Syntax and Parsing */

2011-08-21T12:39:14Z

Syntax and Parsing

← Older revision		Revision as of 12:39, 21 August 2011
Line 253:		Line 253:
	! Character data		! Character data
	\| Unicode characters except for U+0000, non-characters, and control characters (besides space) characters.		\| Unicode characters except for U+0000, non-characters, and control characters (besides space) characters.
	\| XML 1.0 only allows the following Unicode #x9 \| #xA \| #xD \| [#x20-#xD7FF] \| [#xE000-#xFFFD] \| [#x10000-#x10FFFF]		\| XML 1.0 only allows the following Unicode <code>#x9, #xA, #xD, [#x20-#xD7FF], [#xE000-#xFFFD], [#x10000-#x10FFFF]</code>

	XML 1.1 allows all Unicode (including all in 1.0) except for U+0000, U+FFFE, and U+FFFF (i.e., it allows [#x1-#xFFFD] \| [#x10000-#x10FFFF])		XML 1.1 allows all Unicode (including all in 1.0) except for U+0000, U+FFFE, and U+FFFF (i.e., it allows <code>[#x1-#xFFFD] \| [#x10000-#x10FFFF]</code>)

	Both XML 1.0 and 1.1 discourage control-characters and non-characters:		Both XML 1.0 and 1.1 discourage control-characters and non-characters:
	Discouraged in XML 1.0 only: [#xFDE0-#xFDEF] (spec typo?)		Discouraged in XML 1.0 only: <code>[#xFDE0-#xFDEF]</code> (spec typo?)
	Discouraged in XML 1.1 only (these are not allowed at all in 1.0): [#x1-#x8], [#xB-#xC], [#xE-#x1F]		Discouraged in XML 1.1 only (these are not allowed at all in 1.0): <code>[#x1-#x8], [#xB-#xC], [#xE-#x1F]</code>
	Discouraged in XML 1.0-1.1: [#x7F-#x84], [#x86-#x9F], [#xFDD0-#xFDDF], [#x1FFFE-#x1FFFF], [#x2FFFE-#x2FFFF], [#x3FFFE-#x3FFFF], [#x4FFFE-#x4FFFF], [#x5FFFE-#x5FFFF], [#x6FFFE-#x6FFFF], [#x7FFFE-#x7FFFF], [#x8FFFE-#x8FFFF], [#x9FFFE-#x9FFFF], [#xAFFFE-#xAFFFF], [#xBFFFE-#xBFFFF], [#xCFFFE-#xCFFFF], [#xDFFFE-#xDFFFF], [#xEFFFE-#xEFFFF], [#xFFFFE-#xFFFFF], [#x10FFFE-#x10FFFF])		Discouraged in XML 1.0-1.1: <code>[#x7F-#x84], [#x86-#x9F], [#xFDD0-#xFDDF], [#x1FFFE-#x1FFFF], [#x2FFFE-#x2FFFF], [#x3FFFE-#x3FFFF], [#x4FFFE-#x4FFFF], [#x5FFFE-#x5FFFF], [#x6FFFE-#x6FFFF], [#x7FFFE-#x7FFFF], [#x8FFFE-#x8FFFF], [#x9FFFE-#x9FFFF], [#xAFFFE-#xAFFFF], [#xBFFFE-#xBFFFF], [#xCFFFE-#xCFFFF], [#xDFFFE-#xDFFFF], [#xEFFFE-#xEFFFF], [#xFFFFE-#xFFFFF], [#x10FFFE-#x10FFFF]</code>
	\|		\|
	\| Use #x9 \| #xA \| #xD \| [#x20-#xD7FF] \| [#xE000-#xFFFD] \| [#x10000-#x10FFFF] while avoiding [#xFDE0-#xFDEF] (?) ~~and~~ [#x7F-#x84], [#x86-#x9F], [#xFDD0-#xFDDF], [#x1FFFE-#x1FFFF], [#x2FFFE-#x2FFFF], [#x3FFFE-#x3FFFF], [#x4FFFE-#x4FFFF], [#x5FFFE-#x5FFFF], [#x6FFFE-#x6FFFF], [#x7FFFE-#x7FFFF], [#x8FFFE-#x8FFFF], [#x9FFFE-#x9FFFF], [#xAFFFE-#xAFFFF], [#xBFFFE-#xBFFFF], [#xCFFFE-#xCFFFF], [#xDFFFE-#xDFFFF], [#xEFFFE-#xEFFFF], [#xFFFFE-#xFFFFF], [#x10FFFE-#x10FFFF])		\| Use <code>#x9, #xA, #xD, [#x20-#xD7FF], [#xE000-#xFFFD], [#x10000-#x10FFFF]</code> while avoiding <code>[#xFDE0-#xFDEF] (?), [#x7F-#x84], [#x86-#x9F], [#xFDD0-#xFDDF], [#x1FFFE-#x1FFFF], [#x2FFFE-#x2FFFF], [#x3FFFE-#x3FFFF], [#x4FFFE-#x4FFFF], [#x5FFFE-#x5FFFF], [#x6FFFE-#x6FFFF], [#x7FFFE-#x7FFFF], [#x8FFFE-#x8FFFF], [#x9FFFE-#x9FFFF], [#xAFFFE-#xAFFFF], [#xBFFFE-#xBFFFF], [#xCFFFE-#xCFFFF], [#xDFFFE-#xDFFFF], [#xEFFFE-#xEFFFF], [#xFFFFE-#xFFFFF], [#x10FFFE-#x10FFFF]</code>
	\|}		\|}

Brettz9: /* Syntax and Parsing */

2011-08-21T12:34:59Z

Syntax and Parsing

← Older revision		Revision as of 12:34, 21 August 2011
Line 225:		Line 225:
	\|-		\|-
	!CDATA sections		!CDATA sections
	\| <code><![CDATA[...]]></code> is a a bogus comment. The sequence of characters "<code>]]></code>" in content when it does not mark the end of a <code>CDATA</code> section is just regular character data.		\| <code><![CDATA[...]]></code> is a a bogus comment. The sequence of characters "<code>]]></code>" in content when it does not mark the end of a <code>CDATA</code> section is just regular character data. An exception is made for foreign content such as SVG or MathML.
	\| <code><![CDATA[...]]></code> is a <code>CDATA</code> section. The sequence of characters "<code>]]></code>" in content when it does not mark the end of a <code>CDATA</code> section is a well-formedness error.		\| <code><![CDATA[...]]></code> is a <code>CDATA</code> section. The sequence of characters "<code>]]></code>" in content when it does not mark the end of a <code>CDATA</code> section is a well-formedness error.
	\|		\|
	\| Ensure sequence "<code>]]></code>" in content is escaped (not necessary to escape in attribute values). '''Do not use CDATA sections (except possibly for script and style tags--see element-specific behavior below).'''		\| Ensure sequence "<code>]]></code>" in content is escaped (not necessary to escape in attribute values). '''Do not use CDATA sections (except possibly for script and style tags--see element-specific behavior below or for SVG/MathML).'''
	\|-		\|-
	! Unescaped Special Characters		! Unescaped Special Characters
Line 252:		Line 252:
	\|-		\|-
	! Character data		! Character data
			\| Unicode characters except for U+0000, non-characters, and control characters (besides space) characters.
			\| XML 1.0 only allows the following Unicode #x9 \| #xA \| #xD \| [#x20-#xD7FF] \| [#xE000-#xFFFD] \| [#x10000-#x10FFFF]

			XML 1.1 allows all Unicode (including all in 1.0) except for U+0000, U+FFFE, and U+FFFF (i.e., it allows [#x1-#xFFFD] \| [#x10000-#x10FFFF])

			Both XML 1.0 and 1.1 discourage control-characters and non-characters:
			Discouraged in XML 1.0 only: [#xFDE0-#xFDEF] (spec typo?)
			Discouraged in XML 1.1 only (these are not allowed at all in 1.0): [#x1-#x8], [#xB-#xC], [#xE-#x1F]
			Discouraged in XML 1.0-1.1: [#x7F-#x84], [#x86-#x9F], [#xFDD0-#xFDDF], [#x1FFFE-#x1FFFF], [#x2FFFE-#x2FFFF], [#x3FFFE-#x3FFFF], [#x4FFFE-#x4FFFF], [#x5FFFE-#x5FFFF], [#x6FFFE-#x6FFFF], [#x7FFFE-#x7FFFF], [#x8FFFE-#x8FFFF], [#x9FFFE-#x9FFFF], [#xAFFFE-#xAFFFF], [#xBFFFE-#xBFFFF], [#xCFFFE-#xCFFFF], [#xDFFFE-#xDFFFF], [#xEFFFE-#xEFFFF], [#xFFFFE-#xFFFFF], [#x10FFFE-#x10FFFF])
	\|		\|
	\|		\| Use #x9 \| #xA \| #xD \| [#x20-#xD7FF] \| [#xE000-#xFFFD] \| [#x10000-#x10FFFF] while avoiding [#xFDE0-#xFDEF] (?) and [#x7F-#x84], [#x86-#x9F], [#xFDD0-#xFDDF], [#x1FFFE-#x1FFFF], [#x2FFFE-#x2FFFF], [#x3FFFE-#x3FFFF], [#x4FFFE-#x4FFFF], [#x5FFFE-#x5FFFF], [#x6FFFE-#x6FFFF], [#x7FFFE-#x7FFFF], [#x8FFFE-#x8FFFF], [#x9FFFE-#x9FFFF], [#xAFFFE-#xAFFFF], [#xBFFFE-#xBFFFF], [#xCFFFE-#xCFFFF], [#xDFFFE-#xDFFFF], [#xEFFFE-#xEFFFF], [#xFFFFE-#xFFFFF], [#x10FFFE-#x10FFFF])
	\| ~~The valid set of unicode characters in XML 1.0 is limited beyond that in HTML~~ (~~we need to specify this here~~).
	\|
	\|}		\|}

Brettz9: /* Scripts */

2011-08-21T12:01:55Z

Scripts

← Older revision		Revision as of 12:01, 21 August 2011
Line 513:		Line 513:
	! XPath expressions		! XPath expressions
	\| In pre-HTML5 browsers, the XHTML namespace must be used for XHTML and null for HTML. (HTML5 browsers would use the XHTML namespace even in HTML.)		\| In pre-HTML5 browsers, the XHTML namespace must be used for XHTML and null for HTML. (HTML5 browsers would use the XHTML namespace even in HTML.)
	\| In XHTML, all XPath will require a namespace.		\| In XHTML, all XPath will require a namespace unless the elements genuinely have no namespace.
	\|		\|
	\| Detect whether the browser is pre-HTML5 and omit namespaces in XPath expressions if so (otherwise, use a namespace).		\| Detect whether the browser is pre-HTML5 and omit namespaces in XPath expressions if so (otherwise, use a namespace).

Brettz9: /* Scripts */

2011-08-21T11:59:14Z

Scripts

@@ Line 450: / Line 450: @@
+|
 | Ensure one sets <code>innerHTML</code> to well-formed fragments.
 |-
 ! Document.createElement() and namespaces
@@ Line 463: / Line 517: @@
 | Detect whether the browser is pre-HTML5 and omit namespaces in XPath expressions if so (otherwise, use a namespace).
 |}
 === Stylesheets ===

Brettz9: /* MIME Types */ clarification

2011-08-21T09:35:29Z

MIME Types: clarification

← Older revision		Revision as of 09:35, 21 August 2011
Line 31:		Line 31:
	\| Must use <code>text/html</code>.		\| Must use <code>text/html</code>.
	\| Must use an XML MIME type, such as <code>application/xml</code> or <code>application/xhtml+xml</code>.		\| Must use an XML MIME type, such as <code>application/xml</code> or <code>application/xhtml+xml</code>.
	\| It is the MIME type that determines what type of document you are using. Any document, including a document authored with the intention of being XHTML, ~~served as <code>text/html</code>~~ is technically an HTML document.		\| It is the MIME type (which may or may not be determined by file extension) that determines what type of document you are using. Any document served as <code>text/html</code>, including a document authored with the intention of being XHTML, is technically an HTML document.
	\|}		\|}

Brettz9: /* Syntax and Parsing */ fix table

2011-08-21T09:32:46Z

Syntax and Parsing: fix table

← Older revision		Revision as of 09:32, 21 August 2011
Line 93:		Line 93:
	\|The SVG and MathML namespaces must be declared for SVG and MathML elements, respectively, according to the rules defined by ''Namespaces in XML''. The <code>xmlns</code> and <code>xmlns:<var>prefix</var></code> attributes end up in the <code>"http://www.w3.org/2000/xmlns"</code> namespace.		\|The SVG and MathML namespaces must be declared for SVG and MathML elements, respectively, according to the rules defined by ''Namespaces in XML''. The <code>xmlns</code> and <code>xmlns:<var>prefix</var></code> attributes end up in the <code>"http://www.w3.org/2000/xmlns"</code> namespace.
	\|		\|
			\|
	\|-		\|-
	!XLink attributes		!XLink attributes

Brettz9: /* Syntax and Parsing */ Fix table and add info on char. refs

2011-08-21T09:31:47Z

Syntax and Parsing: Fix table and add info on char. refs

← Older revision		Revision as of 09:31, 21 August 2011
Line 179:		Line 179:
	\|-		\|-
	! Raw text elements		! Raw text elements
			\|
	\|		\|
	\|		\|
Line 184:		Line 185:
	\|-		\|-
	! RCDATA elements		! RCDATA elements
			\|
	\|		\|
	\|		\|
Line 189:		Line 191:
	\|-		\|-
	! Foreign elements		! Foreign elements
			\|
	\|		\|
	\|		\|
Line 194:		Line 197:
	\|-		\|-
	! Normal elements		! Normal elements
			\|
	\|		\|
	\|		\|
Line 235:		Line 239:
	\|-		\|-
	!Character References		!Character References
			\| The 'x' in a hexadecimal character reference can be upper-case.
			\| The 'x' in a hexadecimal character reference cannot be upper-case.
	\|		\|
	\|		\| Only use the lower-case 'x' for hexadecimal character references.
	\|
	\|-		\|-
	!Entity References		!Entity References

Brettz9: /* Scripts */ periods

2011-08-21T09:28:02Z

Scripts: periods

← Older revision		Revision as of 09:28, 21 August 2011
Line 434:		Line 434:
	\|-		\|-
	! <code>document.write()</code> and <code>document.writeln()</code>		! <code>document.write()</code> and <code>document.writeln()</code>
	\| Available in HTML		\| Available in HTML.
	\| These cannot be used in XHTML		\| These cannot be used in XHTML.
	\|		\|
	\| Use DOM methods to replace or add content dynamically.		\| Use DOM methods to replace or add content dynamically.
	\|-		\|-
	! <code>innerHTML</code> property		! <code>innerHTML</code> property
	\| Any HTML can be used		\| Any HTML can be used.
	\| The use of this property requires that the string be a well-formed fragment of XML.		\| The use of this property requires that the string be a well-formed fragment of XML.
	\|		\|
Line 453:		Line 453:
	! XPath expressions		! XPath expressions
	\| In pre-HTML5 browsers, the XHTML namespace must be used for XHTML and null for HTML. (HTML5 browsers would use the XHTML namespace even in HTML.)		\| In pre-HTML5 browsers, the XHTML namespace must be used for XHTML and null for HTML. (HTML5 browsers would use the XHTML namespace even in HTML.)
	\| In XHTML, all XPath will require a namespace		\| In XHTML, all XPath will require a namespace.
	\|		\|
	\| Detect whether the browser is pre-HTML5 and omit namespaces in XPath expressions if so (otherwise, use a namespace).		\| Detect whether the browser is pre-HTML5 and omit namespaces in XPath expressions if so (otherwise, use a namespace).