page - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:30:58Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:30, 18 July 2020
Line 1:		Line 1:
	{{stub}}		{{stub}}

	~~<entry-title>~~page~~</entry-title>~~		{{DISPLAYTITLE:page}}

	One particularly interesting use case that seems to keep popping up is that of understanding what a page represents.		One particularly interesting use case that seems to keep popping up is that of understanding what a page represents.

Tantek: re: blog engines, CMS - in practice, they support microformats

2010-07-17T20:27:05Z

re: blog engines, CMS - in practice, they support microformats

← Older revision		Revision as of 20:27, 17 July 2010
Line 111:		Line 111:

	This is a simple/easy rule to remember for publishers.		This is a simple/easy rule to remember for publishers.

	* ... but a lot of publishing platforms (i.e. blog engines, CMSes) would make this pretty difficult in practice. [[User:TobyInk\|TobyInk]] 08:06, 17 July 2010 (UTC)

	For processors/parsers, the rule is simple as well:		For processors/parsers, the rule is simple as well:
Line 121:		Line 119:
	** [[representative-hcard-parsing]]		** [[representative-hcard-parsing]]
	** [[XFN]]		** [[XFN]]


			==== root class on html or body discussion ====
			<div class="discussion">
			* ... but a lot of publishing platforms (i.e. blog engines, CMSes) would make this pretty difficult in practice. [[User:TobyInk\|TobyInk]] 08:06, 17 July 2010 (UTC)
			** Could you provide concrete examples of specific blog engines or CMSes that you've had problems with? The evidence shows otherwise. See [[cms]] etc. for blog engines, CMSes that support microformats now. [[User:Tantek\|Tantek]] 20:27, 17 July 2010 (UTC)
			</div>


	== see also ==		== see also ==
	* [[exploratory-discussions]]		* [[exploratory-discussions]]

TobyInk: /* brainstorming */ difficulty in cmses

2010-07-17T08:06:34Z

brainstorming: difficulty in cmses

← Older revision		Revision as of 08:06, 17 July 2010
Line 111:		Line 111:

	This is a simple/easy rule to remember for publishers.		This is a simple/easy rule to remember for publishers.

			* ... but a lot of publishing platforms (i.e. blog engines, CMSes) would make this pretty difficult in practice. [[User:TobyInk\|TobyInk]] 08:06, 17 July 2010 (UTC)

	For processors/parsers, the rule is simple as well:		For processors/parsers, the rule is simple as well:

Tantek: drafted

2010-07-17T02:18:31Z

drafted

New page

{{stub}}

<entry-title>page</entry-title>

One particularly interesting use case that seems to keep popping up is that of understanding what a page represents.

This page is for collecting research, ideas, and brainstorms about using microformats to represent what a page is (or is about).

[[microformats]] do a good job of allowing authors to easily markup various semantics in pages such as people, events, reviews etc., however, there are only a few examples ([[XFN]], [[rel-me]], [[representative-hcard]]) of using microformats to designate what a whole page means or represents.

== examples ==
Perhaps move this to [[page-examples]] once it grows a bit.

Examples on the web of pages which represent particular types of objects.

=== Wikipedia ===
Wikipedia has pages that represent or are about numerous types of objects. Typically they use specific "infobox" templates to distinguish them.
* ... (links to specific Wikipedia pages that represent specific types of objects)

== formats ==
Perhaps move this to [[page-formats]] once it grows a bit.
=== existing microformats usage ===
==== person ====
* [[XFN]] - use of XFN on a page implies that the page itself is or represents a person.
** [[rel-me]] - rel="me" hyperlinks in particular assert that the current page represents a person, and the destination of the hyperlink also represents the same person.
** There are numerous sites/profiles which support
*** [[hcard-xfn-supporting-friends-lists#Services_with_XFN_supporting_friends_lists|XFN friends lists]]
*** [[hcard-xfn-supporting-friends-lists#Services_with_XFN_rel.3D.22me.22_to_one_external_site|XFN rel-me to connect your profiles]]
* [[representative-hcard]] - representative hCard is a way to publish (and parse for) the fact that particular hCard represents the person that the page is or is about.
** many (most?) of the [[hcard-supporting-user-profiles|numerous sites supporting hCard profiles]] also support representative hCards.

=== Facebook Open Graph Protocol ===
[http://developers.facebook.com/docs/opengraph Facebook's Open Graph Protocol] introduces a meta-tag based format for expressing that a page is or is about a particular type of thing. The following [http://developers.facebook.com/docs/opengraph#types types of objects] are represented:

Activities
* activity
* sport

Businesses
* bar
* company
* cafe
* hotel
* restaurant

Groups
* cause
* sports_league
* sports_team

Organizations
* band
* government
* non_profit
* school
* university

People
* actor
* athlete
* author
* director
* musician
* politician
* public_figure

Places
* city
* country
* landmark
* state_province

Products and Entertainment
* album
* book
* drink
* food
* game
* product
* song
* movie
* tv_show

Websites
* blog
* website
* article

== brainstorming ==
Perhaps move this to [[page-brainstorming]] once it grows a bit.

=== microformat root class on html or body ===
One simple technique that could work for all microformats is to put the root class name of the microformat on the <code><html></code> (permitted in [[HTML5]]), or if not, then the <code><body></code> element.

A page that represents an event:
<source lang=html4strict>
<!DOCTYPE html>
<html class="vevent">
...
</html>
</source>

A page that represents a review:
<source lang=html4strict>
<body class="hreview">
...
</body>
</source>

This is a simple/easy rule to remember for publishers.

For processors/parsers, the rule is simple as well:

* check the <code><html></code> for microformats root class names, if found, treat the page as that type (or types?) of object
* else check the <code><body></code> for microformats root class names, if found, treat the page as that type (or types?) of object
* else perform any format-specific detection
** [[representative-hcard-parsing]]
** [[XFN]]

== see also ==
* [[exploratory-discussions]]