https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=TigtMicroformats Wiki - User contributions [en]2026-05-20T15:41:04ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=link-preview-brainstorming&diff=64880link-preview-brainstorming2015-03-20T05:52:19Z<p>Tigt: /* proposals */ Site names?</p>
<hr />
<div>{{stub}}<br />
<br />
This is part of an effort to define a standard [[link-preview]] microformat.<br />
* [[link-preview-examples]]<br />
* [[link-preview-formats]] - document from Facebook/OG, Google/G+, IE10, Twitter Cards<br />
<br />
== previous related work ==<br />
* [[embed-brainstorming]]<br />
<br />
== proposals ==<br />
General approach:<br />
* publishing: just 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><br />
* parsing: using a [[microformats2]] parser, look for the first [[h-entry]] on the page and use its:<br />
** p-name (called "title" in some other approaches)<br />
** p-summary (called "description" in some other approaches)<br />
** u-url <br />
** u-photo (called "image" in some other approaches)<br />
** u-audio<br />
** u-video<br />
<br />
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?<br />
* The <code>&lt;title&gt;</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.<br />
* The actual "domain name" should be easily computable, but the site name is often different. For example, multiple word names.<br />
* The site name is usually marked up in a nice heading somewhere, so it should be trivial to attach another class name to it.<br />
* 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.<br />
<br />
Examples in the wild: (of pages with h-entry on body)<br />
* http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130221/<br />
** 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=<br />
<br />
== see also ==<br />
* [[link-preview-examples]]<br />
* [[link-preview-formats]]<br />
* [[h-entry]]<br />
* http://indiewebcamp.com/link-preview</div>Tigt