Authoring - Revision history

BenGreen: Removed a link to the worst page on HTML5 I've seen so far.

2009-12-02T10:41:38Z

Removed a link to the worst page on HTML5 I've seen so far.

← Older revision		Revision as of 10:41, 2 December 2009
Line 1:		Line 1:
	Please add tips here on using HTML-5-specific features, and making them compatible with older browsers.		Please add tips here on using HTML-5-specific features, and making them compatible with older browsers.

	~~== Externel tutorial sites ==~~
	* [http://www.html5-knowledge-base.com/ HTML5 Knowledge Base]

	== Getting Internet Explorer to recognize the new elements ==		== Getting Internet Explorer to recognize the new elements ==

Marc Engelhardt: Section added; Link added

2009-11-09T20:08:49Z

Section added; Link added

← Older revision		Revision as of 20:08, 9 November 2009
Line 1:		Line 1:
	Please add tips here on using HTML-5-specific features, and making them compatible with older browsers.		Please add tips here on using HTML-5-specific features, and making them compatible with older browsers.

			== Externel tutorial sites ==
			* [http://www.html5-knowledge-base.com/ HTML5 Knowledge Base]

	== Getting Internet Explorer to recognize the new elements ==		== Getting Internet Explorer to recognize the new elements ==

Enderandpeter: /* Authoring examples */ The last full sentence now begins "The goal..." instead of just "Goal..."

2009-05-11T03:39:47Z

Authoring examples: The last full sentence now begins "The goal..." instead of just "Goal..."

← Older revision		Revision as of 03:39, 11 May 2009
Line 16:		Line 16:
	[work in progress - Rikkert Koppes]		[work in progress - Rikkert Koppes]

	This section is intended to give examples of frequently used markup. For a start, the examples given in the specification should be present and elaborated, next, it can be amended with real world examples. ~~Goal~~ is to concoct a non normative example document for authors accompanying the specification.		This section is intended to give examples of frequently used markup. For a start, the examples given in the specification should be present and elaborated, next, it can be amended with real world examples. The goal is to concoct a non normative example document for authors accompanying the specification.

	* Authoring scientific documents		* Authoring scientific documents

Enderandpeter: /* Authoring examples */ Changed "workd" to "world"

2009-05-11T03:37:49Z

Authoring examples: Changed "workd" to "world"

← Older revision		Revision as of 03:37, 11 May 2009
Line 16:		Line 16:
	[work in progress - Rikkert Koppes]		[work in progress - Rikkert Koppes]

	This section is intended to give examples of frequently used markup. For a start, the examples given in the specification should be present and elaborated, next, it can be amended with real ~~workd~~ examples. Goal is to concoct a non normative example document for authors accompanying the specification.		This section is intended to give examples of frequently used markup. For a start, the examples given in the specification should be present and elaborated, next, it can be amended with real world examples. Goal is to concoct a non normative example document for authors accompanying the specification.

	* Authoring scientific documents		* Authoring scientific documents

Rikkertkoppes: /* Authoring examples */

2009-03-06T17:55:28Z

Authoring examples

← Older revision		Revision as of 17:55, 6 March 2009
Line 14:		Line 14:
	== Authoring examples ==		== Authoring examples ==

	[work in progress ~~[[User:Rikkertkoppes\|mophor]]~~]		[work in progress - Rikkert Koppes]

	This section is intended to give examples of frequently used markup. For a start, the examples given in the specification should be present and elaborated, next, it can be amended with real workd examples. Goal is to concoct a non normative example document for authors accompanying the specification.		This section is intended to give examples of frequently used markup. For a start, the examples given in the specification should be present and elaborated, next, it can be amended with real workd examples. Goal is to concoct a non normative example document for authors accompanying the specification.

Rikkertkoppes: /* Authoring examples */

2009-03-06T17:54:06Z

Authoring examples

← Older revision		Revision as of 17:54, 6 March 2009
Line 13:		Line 13:

	== Authoring examples ==		== Authoring examples ==

			[work in progress [[User:Rikkertkoppes\|mophor]]]

	This section is intended to give examples of frequently used markup. For a start, the examples given in the specification should be present and elaborated, next, it can be amended with real workd examples. Goal is to concoct a non normative example document for authors accompanying the specification.		This section is intended to give examples of frequently used markup. For a start, the examples given in the specification should be present and elaborated, next, it can be amended with real workd examples. Goal is to concoct a non normative example document for authors accompanying the specification.

Rikkertkoppes: /* Authoring scientific documents */

2009-03-06T16:30:00Z

Authoring scientific documents

← Older revision		Revision as of 16:30, 6 March 2009
Line 30:		Line 30:

	The following elements <em title="16:22, 6 March 2009 (UTC)">currently</em> fall in the sectioning content category:		The following elements <em title="16:22, 6 March 2009 (UTC)">currently</em> fall in the sectioning content category:
	* section		* [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-section-element section]
	* nav		* [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-nav-element nav]
	* article		* [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-article-element article]
	* aside		* [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-aside-element aside]

	<pre>		<pre>
Line 48:		Line 48:
	</pre>		</pre>

	Next, the article contains a series of sections, hence the section element. Note the capital "I" is not explicitely marked.		Next, the article contains a series of sections, hence the [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-section-element section] element. Note the capital "I" is not explicitely marked.

	<pre>		<pre>
Line 76:		Line 76:
	[about sectioning content and headers counting]		[about sectioning content and headers counting]

	Figures are not only images, but also for example code listings, in general, anything which can be moved away from the main flow of the document without affecting the document's meaning. One legend element in the figure (if present as first or last child) represents the figure caption.		Figures are not only images, but also for example code listings [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-figure-element], in general, anything which can be moved away from the main flow of the document without affecting the document's meaning. One [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-legend-element legend] element in the figure (if present as first or last child) represents the figure caption.

	<pre>		<pre>
	<figure>		<figure>
	<img src="ericmiller_rdf.png" alt="A graphic representation of the RDF/XML document as given in the next figure.">		<img src="ericmiller_rdf.png" alt="A graphic representation of
	<legend>An RDF graph representing Eric Miller.</legend>		the RDF/XML document as given in the next figure.">
			<legend>An RDF graph representing Eric Miller.</legend>
	</figure>		</figure>
	...		...
Line 88:		Line 89:
	<!-- the actual rdf snippet representinf Eric Miller -->		<!-- the actual rdf snippet representinf Eric Miller -->
	</code></pre>		</code></pre>
	<legend>A chunk of RDF in RDF/XML describing Eric Miller and corresponding to the graph in Figure A.</legend>		<legend>A chunk of RDF in RDF/XML describing Eric Miller and
			corresponding to the graph in Figure A.</legend>
	</figure>		</figure>
	</pre>		</pre>
Line 94:		Line 96:
	Note that the phrase "Figure A" is not part of the legend. This is typically handled through CSS [REF NEEDED].		Note that the phrase "Figure A" is not part of the legend. This is typically handled through CSS [REF NEEDED].

	In the documents, some quotes from the text are extracted as an eye-catcher. These quotes, marked with a q element, are additionally marked with an aside element.		In the documents, some quotes from the text are extracted as an eye-catcher. These quotes, marked with a [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-q-element q] element, are additionally marked with an [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-aside-element aside] element.

	<pre>		<pre>
	<aside>		<aside>
	<q>URIs have global scope. ~~Associating a URI with a resource means that anyone can link to it, refer to it, or retrieve a representation~~ of it.</q>		<q>URIs have global scope [...] of it.</q>
	</aside>		</aside>
	</pre>		</pre>

Rikkertkoppes: /* Authoring examples */

2009-03-06T16:22:46Z

Authoring examples

← Older revision		Revision as of 16:22, 6 March 2009
Line 18:		Line 18:
	* Authoring scientific documents		* Authoring scientific documents
	* Authoring article based pages (news, blogs)		* Authoring article based pages (news, blogs)

			=== Authoring scientific documents ===

			Since the origins of HTML lie in the markup of scientific documents [REF NEEDED], let us start with markup examples for such a document. This will allow us to discuss HTML examples in a layered way, starting relatively simple.

			Consider the first page of the document "The Semantic Web Revisited" by Nigel Shadbolt, Wendy Hall and Tim Berners-Lee [http://geospatialsemanticweb.com/wp-content/uploads/2006/07/01637364.pdf], for clarity [http://www.rikkertkoppes.com/whatwg/examples/semantic_web_revisited_page_01.PNG pictured here]. We skip the orangish editor info at the top and start with the document header.

			The document contains one article, hence the [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-article-element article] element is a suitable choice here, starting with a [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-header-element header] element.

			Notice the nested [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-address-element address] element representing the document authors. The address element represents the contact information for the sectioning content it applies to, which is, in this case, the article element.

			The following elements <em title="16:22, 6 March 2009 (UTC)">currently</em> fall in the sectioning content category:
			* section
			* nav
			* article
			* aside

			<pre>
			<article>
			<header>
			<h1>The Semantic Web Revisited</h1>
			<address>
			<p>Nigel Shadbolt and Wendy Hall, University of Southampton</p>
			<p>Tim Berners-Lee, Massachusetts Institute of Technology</p>
			</address>
			</header>
			<!-- rest of the document -->
			</article>
			</pre>

			Next, the article contains a series of sections, hence the section element. Note the capital "I" is not explicitely marked.

			<pre>
			<article>
			<!-- header -->
			<section>
			<p>In the 50 years [...] instantaneously.</p>
			<p>Fifty years ago [...] research.</p>
			</section>
			<!-- rest of the document -->
			</article>
			</pre>

			<pre>
			<article>
			<!-- first part of the document -->
			<section>
			<h2>From documents to data and information</h2>
			<p>The original [...] unrealized.</p>
			<p>A Web of data [...] Web.</p>
			<p>The article included [...] Web.</p>
			</section>
			<!-- rest of the document -->
			</article>
			</pre>

			[about sectioning content and headers counting]

			Figures are not only images, but also for example code listings, in general, anything which can be moved away from the main flow of the document without affecting the document's meaning. One legend element in the figure (if present as first or last child) represents the figure caption.

			<pre>
			<figure>
			<img src="ericmiller_rdf.png" alt="A graphic representation of the RDF/XML document as given in the next figure.">
			<legend>An RDF graph representing Eric Miller.</legend>
			</figure>
			...
			<figure>
			<pre><code class="language-rdf/xml">
			<!-- the actual rdf snippet representinf Eric Miller -->
			</code></pre>
			<legend>A chunk of RDF in RDF/XML describing Eric Miller and corresponding to the graph in Figure A.</legend>
			</figure>
			</pre>

			Note that the phrase "Figure A" is not part of the legend. This is typically handled through CSS [REF NEEDED].

			In the documents, some quotes from the text are extracted as an eye-catcher. These quotes, marked with a q element, are additionally marked with an aside element.

			<pre>
			<aside>
			<q>URIs have global scope. Associating a URI with a resource means that anyone can link to it, refer to it, or retrieve a representation of it.</q>
			</aside>
			</pre>

Rikkertkoppes at 10:49, 4 March 2009

2009-03-04T10:49:38Z

← Older revision		Revision as of 10:49, 4 March 2009
Line 11:		Line 11:

	([http://blog.whatwg.org/supporting-new-elements-in-ie More details].)		([http://blog.whatwg.org/supporting-new-elements-in-ie More details].)

			== Authoring examples ==

			This section is intended to give examples of frequently used markup. For a start, the examples given in the specification should be present and elaborated, next, it can be amended with real workd examples. Goal is to concoct a non normative example document for authors accompanying the specification.

			* Authoring scientific documents
			* Authoring article based pages (news, blogs)

Annevk at 14:54, 8 January 2009

2009-01-08T14:54:37Z

← Older revision		Revision as of 14:54, 8 January 2009
Line 10:		Line 10:
	</pre>		</pre>

	([http://~~ejohn~~.org/~~blog/html5~~-~~shiv/~~ More details].)		([http://blog.whatwg.org/supporting-new-elements-in-ie More details].)