semantic-xhtml-design-principles - Revision history

RyanKing: Reverted edits by SitdaRouca (Talk) to last version by Brian

2009-01-06T19:53:29Z

Reverted edits by SitdaRouca (Talk) to last version by Brian

← Older revision		Revision as of 19:53, 6 January 2009
Line 1:		Line 1:
	~~domviricdron~~
	<h1>Semantic XHTML Design Principles</h1>		<h1>Semantic XHTML Design Principles</h1>

Line 5:		Line 4:

	==Semantic XHTML and Microformats==		==Semantic XHTML and Microformats==
	(from Tantek ~~Ãelik~~ on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])		(from Tantek Çelik on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])

	Note that microformats use semantic XHTML, but not all use of semantic		Note that microformats use semantic XHTML, but not all use of semantic

SitdaRouca: chilili

2009-01-06T17:41:54Z

chilili

← Older revision		Revision as of 17:41, 6 January 2009
Line 1:		Line 1:
			domviricdron
	<h1>Semantic XHTML Design Principles</h1>		<h1>Semantic XHTML Design Principles</h1>

Line 4:		Line 5:

	==Semantic XHTML and Microformats==		==Semantic XHTML and Microformats==
	(from Tantek ~~Çelik~~ on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])		(from Tantek Ãelik on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])

	Note that microformats use semantic XHTML, but not all use of semantic		Note that microformats use semantic XHTML, but not all use of semantic

Brian: Reverted edits by OlotrOcroe (Talk) to last version by Tantek

2008-12-20T18:58:29Z

Reverted edits by OlotrOcroe (Talk) to last version by Tantek

← Older revision		Revision as of 18:58, 20 December 2008
Line 1:		Line 1:
	~~cnarooloel~~
	<h1>Semantic XHTML Design Principles</h1>		<h1>Semantic XHTML Design Principles</h1>

Line 5:		Line 4:

	==Semantic XHTML and Microformats==		==Semantic XHTML and Microformats==
	(from Tantek ~~Ãelik~~ on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])		(from Tantek Çelik on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])

	Note that microformats use semantic XHTML, but not all use of semantic		Note that microformats use semantic XHTML, but not all use of semantic

OlotrOcroe: trletoc4tta

2008-12-19T23:38:15Z

trletoc4tta

← Older revision		Revision as of 23:38, 19 December 2008
Line 1:		Line 1:
			cnarooloel
	<h1>Semantic XHTML Design Principles</h1>		<h1>Semantic XHTML Design Principles</h1>

Line 4:		Line 5:

	==Semantic XHTML and Microformats==		==Semantic XHTML and Microformats==
	(from Tantek ~~Çelik~~ on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])		(from Tantek Ãelik on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])

	Note that microformats use semantic XHTML, but not all use of semantic		Note that microformats use semantic XHTML, but not all use of semantic

Tantek: moved context prolog into the template

2007-10-21T22:20:51Z

moved context prolog into the template

← Older revision		Revision as of 22:20, 21 October 2007
Line 1:		Line 1:
	<h1>Semantic XHTML Design Principles</h1>		<h1>Semantic XHTML Design Principles</h1>

	'''Note: the Semantic XHTML Design Principles were written primarily within the context of developing [[hcard\|hCard]] and [[hcalendar\|hCalendar]], thus it may be easier to understand this page in the context of the [[hcard-design-methodology\|hCard design methodology]] (i.e. read that first). [[User:Tantek\|Tantek]]'''

	{{semantic-xhtml-design-principles}}		{{semantic-xhtml-design-principles}}

Tantek: use templated for semantic-xhtml-design-principles

2007-10-21T22:11:49Z

use templated for semantic-xhtml-design-principles

← Older revision		Revision as of 22:11, 21 October 2007
Line 3:		Line 3:
	'''Note: the Semantic XHTML Design Principles were written primarily within the context of developing [[hcard\|hCard]] and [[hcalendar\|hCalendar]], thus it may be easier to understand this page in the context of the [[hcard-design-methodology\|hCard design methodology]] (i.e. read that first). [[User:Tantek\|Tantek]]'''		'''Note: the Semantic XHTML Design Principles were written primarily within the context of developing [[hcard\|hCard]] and [[hcalendar\|hCalendar]], thus it may be easier to understand this page in the context of the [[hcard-design-methodology\|hCard design methodology]] (i.e. read that first). [[User:Tantek\|Tantek]]'''

	XHTML is built on XML, and thus XHTML-based formats can be used not only for convenient display presentation, but also for general-purpose data exchange. In many ways, XHTML-based formats exemplify the best of both HTML and XML worlds. However, when building XHTML-based formats, it helps to have a guiding set of principles.		{{semantic-xhtml-design-principles}}

	# Reuse the schema (names, objects, properties, values, types, hierarchies, constraints) as much as possible from pre-existing, established, well-supported standards by reference. Avoid restating constraints expressed in the source standard. Informative mentions are ok.
	~~## For types with multiple components, use nested elements with class names equivalent to the names of the components.~~
	~~## Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.~~
	~~# Use the most accurately precise semantic XHTML building block for each object etc.~~
	# Otherwise use a generic structural element (e.g. <code><span></code> or <code><div></code>), or the appropriate contextual element (e.g. an <code><li></code> inside a <code><ul></code> or <code><ol></code>).
	~~# Use class names based on names from the original schema, unless the [[~~semantic-xhtml\|semantic XHTML]] building block precisely represents that part of the original schema. If names in the source schema are case-insensitive, then use an all lowercase equivalent. Components names implicit in prose (rather than explicit in the defined schema) should also use lowercase equivalents for ease of use. Spaces in component names become dash '-' characters.
	# Finally, if the format of the data according to the original schema is too long and/or not human-friendly, use <code><abbr></code> instead of a generic structural element, and place the literal data into the 'title' attribute (where abbr expansions go), and the more brief and human-readable equivalent into the element itself. Further informative explanation of this use of <code><abbr></code>: [[abbr-design-pattern]], [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved], and [http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility] aka "abbr-design-pattern considered harmful."

	==Semantic XHTML and Microformats==		==Semantic XHTML and Microformats==

Tantek: added reference to hcard-design-methodology context

2007-10-21T21:59:59Z

added reference to hcard-design-methodology context

← Older revision		Revision as of 21:59, 21 October 2007
Line 1:		Line 1:
	=Semantic XHTML Design Principles=		<h1>Semantic XHTML Design Principles</h1>

	~~__TOC__~~		'''Note: the Semantic XHTML Design Principles were written primarily within the context of developing [[hcard\|hCard]] and [[hcalendar\|hCalendar]], thus it may be easier to understand this page in the context of the [[hcard-design-methodology\|hCard design methodology]] (i.e. read that first). [[User:Tantek\|Tantek]]'''

	XHTML is built on XML, and thus XHTML-based formats can be used not only for convenient display presentation, but also for general-purpose data exchange. In many ways, XHTML-based formats exemplify the best of both HTML and XML worlds. However, when building XHTML-based formats, it helps to have a guiding set of principles.		XHTML is built on XML, and thus XHTML-based formats can be used not only for convenient display presentation, but also for general-purpose data exchange. In many ways, XHTML-based formats exemplify the best of both HTML and XML worlds. However, when building XHTML-based formats, it helps to have a guiding set of principles.

Tantek: Reverted edit of QuoHle, changed back to last version by RobertBachmann

2007-06-23T16:55:32Z

Reverted edit of QuoHle, changed back to last version by RobertBachmann

@@ Line 9: / Line 9: @@
 ## Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.
 # Use the most accurately precise semantic XHTML building block for each object etc.
-# Otherwise use a generic structural element (e.g. <code>
+# Otherwise use a generic structural element (e.g. <code>&lt;span&gt;</code> or <code>&lt;div&gt;</code>), or the appropriate contextual element (e.g. an <code>&lt;li&gt;</code> inside a <code>&lt;ul&gt;</code> or <code>&lt;ol&gt;</code>).

QuoHle at 12:35, 23 June 2007

2007-06-23T12:35:08Z

@@ Line 9: / Line 9: @@
 ## Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.
 # Use the most accurately precise semantic XHTML building block for each object etc.
-# Otherwise use a generic structural element (e.g. <code>&lt;span&gt;</code> or <code>&lt;div&gt;</code>), or the appropriate contextual element (e.g. an <code>&lt;li&gt;</code> inside a <code>&lt;ul&gt;</code> or <code>&lt;ol&gt;</code>).
+# Otherwise use a generic structural element (e.g. <code>

RobertBachmann: Reverted edit of AfsU77, changed back to last version by JamesCraig

2007-05-28T13:19:02Z

Reverted edit of AfsU77, changed back to last version by JamesCraig

@@ Line 9: / Line 9: @@
 ## Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.
 # Use the most accurately precise semantic XHTML building block for each object etc.
-# Otherwise use a generic structural element (e.g. <code>
+# Otherwise use a generic structural element (e.g. <code>&lt;span&gt;</code> or <code>&lt;div&gt;</code>), or the appropriate contextual element (e.g. an <code>&lt;li&gt;</code> inside a <code>&lt;ul&gt;</code> or <code>&lt;ol&gt;</code>).