link-preview-brainstorming - Revision history

Tantek: -=

2016-12-08T01:24:11Z

← Older revision		Revision as of 01:24, 8 December 2016
Line 32:		Line 32:
	* A "site microformat" may scratch the itch of those who like putting up invisible rel=author and similar data, allow for explicit site-wide legal disclaimers vs. page-level (like Tumblr's policies vs. the content its users copyright on their blogs on a tumblr subdomain), site-wide tags/categories, and other various publisher vs. author distinctions.		* A "site microformat" may scratch the itch of those who like putting up invisible rel=author and similar data, allow for explicit site-wide legal disclaimers vs. page-level (like Tumblr's policies vs. the content its users copyright on their blogs on a tumblr subdomain), site-wide tags/categories, and other various publisher vs. author distinctions.

	=== Examples in the wild ===		== Examples in the wild ==
	Examples on the web of pages with h-entry on body:		Examples on the web of pages with h-entry on body:
	* http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130221/		* http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130221/

Tantek: subheads for brainstorming

2016-12-08T01:23:51Z

subheads for brainstorming

← Older revision		Revision as of 01:23, 8 December 2016
Line 9:		Line 9:

	== proposals ==		== proposals ==
	General ~~approach~~:		General approaches:
	* publishing:
	** in general: use [[h-entry]] on the <code><body></code> element with a few additions like <code>u-photo</code>, <code>u-audio</code>, <code>u-video</code>		=== publishing ===
	** use [[h-card]] for pages of people or organizations,		* In general: use [[h-entry]] on the <code><body></code> element with a few additions like <code>u-photo</code>, <code>u-audio</code>, <code>u-video</code>
	** [[h-product]] for product pages		* Use [[h-card]] for pages of people or organizations,
	** (or whatever top level object the page represents)		* [[h-product]] for product pages
	* parsing~~: using~~ a [[microformats2]] parser, look for the first <code>h-*</code> on the page and use its:		* (or whatever top level object the page represents)
	** p-name (called "title" in some other approaches)
	** p-summary (called "description" in some other approaches)		=== parsing ===
	** u-url		Using a [[microformats2]] parser, look for the first <code>h-*</code> on the page and use its:
	** u-photo (called "image" in some other approaches)		* p-name (called "title" in some other approaches)
	** u-audio		* p-summary (called "description" in some other approaches)
	** u-video		* u-url
			* u-photo (called "image" in some other approaches)
			* u-audio
			* u-video

	Existing link preview schemes allow differentiating the "page name" from the "site name," such as OpenGraph's <code>og:site_name</code>/<code>og:title</code> and Twitter Cards's <code>twitter:domain</code>/<code>twitter:title</code>. Is this worth investigating?		Existing link preview schemes allow differentiating the "page name" from the "site name," such as OpenGraph's <code>og:site_name</code>/<code>og:title</code> and Twitter Cards's <code>twitter:domain</code>/<code>twitter:title</code>. Is this worth investigating?
Line 29:		Line 32:
	* A "site microformat" may scratch the itch of those who like putting up invisible rel=author and similar data, allow for explicit site-wide legal disclaimers vs. page-level (like Tumblr's policies vs. the content its users copyright on their blogs on a tumblr subdomain), site-wide tags/categories, and other various publisher vs. author distinctions.		* A "site microformat" may scratch the itch of those who like putting up invisible rel=author and similar data, allow for explicit site-wide legal disclaimers vs. page-level (like Tumblr's policies vs. the content its users copyright on their blogs on a tumblr subdomain), site-wide tags/categories, and other various publisher vs. author distinctions.

	Examples in the wild~~: (~~of pages with h-entry on body)		=== Examples in the wild ===
			Examples on the web of pages with h-entry on body:
	* http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130221/		* http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130221/
	** see parsed version: http://microformat2-node.jit.su/?url=http%3A%2F%2Fwww.w3.org%2FTR%2F2013%2FWD-css-counter-styles-3-20130221%2F&callback=&filters=		** see parsed version: http://microformat2-node.jit.su/?url=http%3A%2F%2Fwww.w3.org%2FTR%2F2013%2FWD-css-counter-styles-3-20130221%2F&callback=&filters=
			* ...

	== see also ==		== see also ==

Tantek: /* proposals */ expand proposal to include specific other types of body objects

2015-06-01T05:38:05Z

proposals: expand proposal to include specific other types of body objects

← Older revision		Revision as of 05:38, 1 June 2015
Line 10:		Line 10:
	== proposals ==		== proposals ==
	General approach:		General approach:
	* publishing: ~~just~~ use [[h-entry]] ~~(or whatever top level object the page represents)~~ on the <code><body></code> element with a few additions like <code>u-photo</code>, <code>u-audio</code>, <code>u-video</code>		* publishing:
			** in general: use [[h-entry]] on the <code><body></code> element with a few additions like <code>u-photo</code>, <code>u-audio</code>, <code>u-video</code>
			** use [[h-card]] for pages of people or organizations,
			** [[h-product]] for product pages
			** (or whatever top level object the page represents)
	* parsing: using a [[microformats2]] parser, look for the first <code>h-*</code> on the page and use its:		* parsing: using a [[microformats2]] parser, look for the first <code>h-*</code> on the page and use its:
	** p-name (called "title" in some other approaches)		** p-name (called "title" in some other approaches)

Tantek: /* proposals */ code not link

2015-04-23T18:37:19Z

proposals: code not link

← Older revision		Revision as of 18:37, 23 April 2015
Line 11:		Line 11:
	General approach:		General approach:
	* publishing: just use [[h-entry]] (or whatever top level object the page represents) on the <code><body></code> element with a few additions like <code>u-photo</code>, <code>u-audio</code>, <code>u-video</code>		* publishing: just use [[h-entry]] (or whatever top level object the page represents) on the <code><body></code> element with a few additions like <code>u-photo</code>, <code>u-audio</code>, <code>u-video</code>
	* parsing: using a [[microformats2]] parser, look for the first [[h-*]] on the page and use its:		* parsing: using a [[microformats2]] parser, look for the first <code>h-*</code> on the page and use its:
	** p-name (called "title" in some other approaches)		** p-name (called "title" in some other approaches)
	** p-summary (called "description" in some other approaches)		** p-summary (called "description" in some other approaches)

Tantek: use appropriate h-* object for the page, parse first h-* object on the page

2015-04-23T18:27:50Z

use appropriate h-* object for the page, parse first h-* object on the page

← Older revision		Revision as of 18:27, 23 April 2015
Line 10:		Line 10:
	== proposals ==		== proposals ==
	General approach:		General approach:
	* publishing: just use [[h-entry]] on the <code><body></code> element with a few additions like <code>u-photo</code>, <code>u-audio</code>, <code>u-video</code>		* publishing: just use [[h-entry]] (or whatever top level object the page represents) on the <code><body></code> element with a few additions like <code>u-photo</code>, <code>u-audio</code>, <code>u-video</code>
	* parsing: using a [[microformats2]] parser, look for the first [[h-~~entry~~]] on the page and use its:		* parsing: using a [[microformats2]] parser, look for the first [[h-*]] on the page and use its:
	** p-name (called "title" in some other approaches)		** p-name (called "title" in some other approaches)
	** p-summary (called "description" in some other approaches)		** p-summary (called "description" in some other approaches)

Tigt: /* proposals */ Site names?

2015-03-20T05:52:19Z

proposals: Site names?

← Older revision		Revision as of 05:52, 20 March 2015
Line 18:		Line 18:
	** u-audio		** u-audio
	** u-video		** u-video

			Existing link preview schemes allow differentiating the "page name" from the "site name," such as OpenGraph's <code>og:site_name</code>/<code>og:title</code> and Twitter Cards's <code>twitter:domain</code>/<code>twitter:title</code>. Is this worth investigating?
			* The <code><title></code> element usually features both, and sometimes a tagline. It's invalid to nest tags inside of it, so breaking it down is probably a bad idea.
			* The actual "domain name" should be easily computable, but the site name is often different. For example, multiple word names.
			* The site name is usually marked up in a nice heading somewhere, so it should be trivial to attach another class name to it.
			* A "site microformat" may scratch the itch of those who like putting up invisible rel=author and similar data, allow for explicit site-wide legal disclaimers vs. page-level (like Tumblr's policies vs. the content its users copyright on their blogs on a tumblr subdomain), site-wide tags/categories, and other various publisher vs. author distinctions.

	Examples in the wild: (of pages with h-entry on body)		Examples in the wild: (of pages with h-entry on body)

Tantek: more see also

2014-02-24T04:04:45Z

more see also

← Older revision		Revision as of 04:04, 24 February 2014
Line 24:		Line 24:

	== see also ==		== see also ==
			* [[link-preview-examples]]
			* [[link-preview-formats]]
	* [[h-entry]]		* [[h-entry]]
			* http://indiewebcamp.com/link-preview

Tantek: /* proposals */ )

2013-04-13T00:32:34Z

proposals: )

← Older revision		Revision as of 00:32, 13 April 2013
Line 15:		Line 15:
	** p-summary (called "description" in some other approaches)		** p-summary (called "description" in some other approaches)
	** u-url		** u-url
	** u-photo (called "image" in some other approaches		** u-photo (called "image" in some other approaches)
	** u-audio		** u-audio
	** u-video		** u-video

Tantek: previous work - embed-brainstorming

2013-04-08T18:41:42Z

previous work - embed-brainstorming

← Older revision		Revision as of 18:41, 8 April 2013
Line 4:		Line 4:
	* [[link-preview-examples]]		* [[link-preview-examples]]
	* [[link-preview-formats]] - document from Facebook/OG, Google/G+, IE10, Twitter Cards		* [[link-preview-formats]] - document from Facebook/OG, Google/G+, IE10, Twitter Cards

			== previous related work ==
			* [[embed-brainstorming]]

	== proposals ==		== proposals ==

Tantek: draft a stub with summary of current thinking

2013-03-01T02:07:42Z

draft a stub with summary of current thinking

New page

{{stub}}

This is part of an effort to define a standard [[link-preview]] microformat.
* [[link-preview-examples]]
* [[link-preview-formats]] - document from Facebook/OG, Google/G+, IE10, Twitter Cards

== proposals ==
General approach:
* publishing: just use [[h-entry]] on the <code><body></code> element with a few additions like <code>u-photo</code>, <code>u-audio</code>, <code>u-video</code>
* parsing: using a [[microformats2]] parser, look for the first [[h-entry]] on the page and use its:
** p-name (called "title" in some other approaches)
** p-summary (called "description" in some other approaches)
** u-url
** u-photo (called "image" in some other approaches
** u-audio
** u-video

Examples in the wild: (of pages with h-entry on body)
* http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130221/
** see parsed version: http://microformat2-node.jit.su/?url=http%3A%2F%2Fwww.w3.org%2FTR%2F2013%2FWD-css-counter-styles-3-20130221%2F&callback=&filters=

== see also ==
* [[h-entry]]