posh-patterns - Revision history

Tantek: /* Comments */ comment on a comment regarding comments using blockquotes

2009-07-07T23:54:47Z

Comments: comment on a comment regarding comments using blockquotes

← Older revision		Revision as of 23:54, 7 July 2009
Line 58:		Line 58:
	<div class="discussion">		<div class="discussion">
	* It's good embrace of underused semantic mark-up, but authors should consider whether the comments included on their pages are really ''quotes'', since in most cases, a comment written in response to a post is original content, published for the first time, not a quote from another source. Consider separate [[hAtom]] entries for each comment instead. --[[User:BenWard\|BenWard]] 22:09, 7 July 2009 (UTC)		* It's good embrace of underused semantic mark-up, but authors should consider whether the comments included on their pages are really ''quotes'', since in most cases, a comment written in response to a post is original content, published for the first time, not a quote from another source. Consider separate [[hAtom]] entries for each comment instead. --[[User:BenWard\|BenWard]] 22:09, 7 July 2009 (UTC)
			** But comments are exactly that - "a quote from another source" - they are words quoted from another (other than the site/blog owner itself typically) source, a person in this case, rather than a written work. I think the [http://www.w3.org/TR/html401/struct/text.html#h-9.2.2 HTML 4.01 definition of blockquote] is sufficiently broad to allow for this interpretation, hence the markup suggestion in the first place. Note that since there is no written (online or printed) source that is being referenced, that is exactly why I recommend using the <code>cite</code> element in this case to markup just the commenter's name, since the commenter is the source. -- [[User:Tantek\|Tantek]] 23:54, 7 July 2009 (UTC)
	</div>		</div>

Abernier: /* Comments */ Adding
tags within blockquotes in comments-pattern

2009-07-07T22:24:25Z

Comments: Adding <p> tags within blockquotes in comments-pattern

← Older revision		Revision as of 22:24, 7 July 2009
Line 48:		Line 48:
	<li>		<li>
	<cite><!-- user's name goes here --></cite>:		<cite><!-- user's name goes here --></cite>:
	<blockquote>		<blockquote><p>
	<!-- comment goes here -->		<!-- comment goes here -->
	</blockquote>		</p></blockquote>
	</li>		</li>
	...		...

BenWard: /* Comments */ Naysaying documentation regarding blockquote for comments, added suggestion + link to hAtom

2009-07-07T22:09:21Z

Comments: Naysaying documentation regarding blockquote for comments, added suggestion + link to hAtom

← Older revision		Revision as of 22:09, 7 July 2009
Line 55:		Line 55:
	</ol>		</ol>
	</source>		</source>

			<div class="discussion">
			* It's good embrace of underused semantic mark-up, but authors should consider whether the comments included on their pages are really ''quotes'', since in most cases, a comment written in response to a post is original content, published for the first time, not a quote from another source. Consider separate [[hAtom]] entries for each comment instead. --[[User:BenWard\|BenWard]] 22:09, 7 July 2009 (UTC)
			</div>

	=== Bibliography ===		=== Bibliography ===

Abernier: /* patterns */ Adding bibliography pattern

2009-07-07T21:50:44Z

patterns: Adding bibliography pattern

← Older revision		Revision as of 21:50, 7 July 2009
Line 47:		Line 47:
	<ol>		<ol>
	<li>		<li>
	<cite><!-- user's name go here --></cite>:		<cite><!-- user's name goes here --></cite>:
	<blockquote>		<blockquote>
	<!-- comment go here -->		<!-- comment goes here -->
	</blockquote>		</blockquote>
			</li>
			...
			</ol>
			</source>

			=== Bibliography ===
			Suggested in [http://tantek.com/presentations/2005/09/elements-of-xhtml/#slide43 The Elements of Meaningful XHTML]:

			<source lang="html4strict">
			<ol>
			<li>
			<cite><!-- your reference goes here --></cite>
	</li>		</li>
	...		...

Abernier: /* POSH patterns */ Adding the comments posh-pattern

2009-07-07T21:41:06Z

POSH patterns: Adding the comments posh-pattern

@@ Line 41: / Line 41: @@
 </source>
 == related ==
 * [[posh]]
 * [[poshformats]]

Tantek: emphasize stub nature of page, encourage analysis

2009-05-05T20:09:02Z

emphasize stub nature of page, encourage analysis

← Older revision		Revision as of 20:09, 5 May 2009
Line 5:		Line 5:
	For a longer description of POSH patterns, see [http://adactio.com/journal/1287/ Jeremy Keith's blog post: POSH Patterns].		For a longer description of POSH patterns, see [http://adactio.com/journal/1287/ Jeremy Keith's blog post: POSH Patterns].

	This page is a stub and could use your help in expanding it. Please read [[posh#Resources\|POSH resources]], and add good examples you find there.		'''This page is a stub and could use your help in expanding it. Please read [[posh#Resources\|POSH resources]], and add good examples you find there along with some analysis.'''

	== patterns ==		== patterns ==

Tantek: added Jeremy Keith's blogpost on posh patterns and navigation pattern from today's IRC discussion

2009-04-28T15:23:04Z

added Jeremy Keith's blogpost on posh patterns and navigation pattern from today's IRC discussion

@@ Line 2: / Line 2: @@
 To help discover and make it easier to write proper plain old semantic html ([[posh]]), this page documents known patterns of POSH markup used in the wild (no theoretical patterns please, markup from actual URLs on the public web), especially when there is some amount of analysis regarding the patterns.
 This page is a stub and could use your help in expanding it.  Please read [[posh#Resources|POSH resources]], and add good examples you find there.
 == related ==
 * [[posh]]
 * [[poshformats]]

Tantek: drafted

2009-04-28T14:57:32Z

drafted

New page

= POSH patterns =

To help discover and make it easier to write proper plain old semantic html ([[posh]]), this page documents known patterns of POSH markup used in the wild (no theoretical patterns please, markup from actual URLs on the public web), especially when there is some amount of analysis regarding the patterns.

This page is a stub and could use your help in expanding it. Please read [[posh#Resources|POSH resources]], and add good examples you find there.

== related ==
* [[posh]]
* [[poshformats]]