link-preview-brainstorming

(Difference between revisions)

Jump to: navigation, search
(proposals: code not link)
(proposals: expand proposal to include specific other types of body objects)
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>&lt;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>&lt;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)

Revision as of 05:38, 1 June 2015

This article is a stub. You can help the microformats.org wiki by expanding it.

This is part of an effort to define a standard link-preview microformat.

previous related work

proposals

General approach:

Existing link preview schemes allow differentiating the "page name" from the "site name," such as OpenGraph's og:site_name/og:title and Twitter Cards's twitter:domain/twitter:title. Is this worth investigating?

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

see also

link-preview-brainstorming was last modified: Wednesday, December 31st, 1969

Views