Difference between revisions of "link-preview-brainstorming"

From Microformats Wiki
Jump to navigation Jump to search
(more see also)
(→‎proposals: Site names?)
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>&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.
 +
* 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)

Revision as of 05:52, 20 March 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:

  • publishing: just use h-entry on the <body> element with a few additions like u-photo, u-audio, u-video
  • 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

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)

see also