link-preview-brainstorming: Difference between revisions
Jump to navigation
Jump to search
(use appropriate h-* object for the page, parse first h-* object on the page) |
(→proposals: code not link) |
||
| 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 | * 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) | ||
Revision as of 18:37, 23 April 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.
- link-preview-examples
- link-preview-formats - document from Facebook/OG, Google/G+, IE10, Twitter Cards
proposals
General approach:
- publishing: just use h-entry (or whatever top level object the page represents) on the
<body>element with a few additions likeu-photo,u-audio,u-video - 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-summary (called "description" in some other approaches)
- 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 og:site_name/og:title and Twitter Cards's twitter:domain/twitter:title. Is this worth investigating?
- The
<title>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)