microformats2-implied-properties
<entry-title>microformats 2 implied properties</entry-title>
summary
As part of the further simplifications in microformats-2, the following generic properties are automatically implied by microformats with only a root class name with certain common semantic markup patterns.
p-nameon elements in generalu-urlon hyperlinks (<a href>) elementsu-photoon images (<img src>) elements
and combinations thereof.
root class only and name property
Web pages with microformats nearly always markup proper nouns, which have a primary label of some sort, commonly known as a name.
Thus if a microformat only has a root class name and no properties, then the entire text contents of the element is parsed as the p-name property of the microformat.
Markup example:
Simple person reference:
<span class="h-card">Frances Berriman</span>
Parsed JSON with implied name property:
{
"type": ["h-card"],
"properties": {
"name": ["Frances Berriman"]
}
}
to-do:
- try examples with organizations, events, products (however note that those are almost always capitalized thus implying proper noun / name semantics)
use-cases:
- every single proper noun on any web page.
issues:
aside name vs fn
In short, why use 'name' instead of the well established 'fn' from existing microformats? (per naming-principle etc.) Per feedback:
- from microformats mailing-lists over the years
- numerous individuals preferring 'name'
- asking why 'fn' repeatedly despite FAQ
- Google Rich Snippets renaming 'fn' as 'name' in RDFa and microdata variants of vocabularies
- ...
Choosing to use 'name' as the generic term moving forward instead of 'fn' - the benefits outweigh costs.
hyperlink and url property
A significant proportion of proper noun references on web pages are a hyperlink to a page about that proper noun, AKA a URL for a proper noun.
Thus if a microformat is on a hyperlink element with only a root class name and no properties, then in addition to implying the name from its text contents, the href of the element is parsed as the u-url property of the microformat.
Markup example:
Simple hyperlinked person reference
<a class="h-card" href="http://benward.me">Ben Ward</a>
Parsed JSON:
{
"type": ["h-card"],
"properties": {
"name": ["Ben Ward"],
"url": ["http://benward.me"]
}
}
to-do:
- try examples with organizations, events, products
use-cases:
- nearly every link to a person ever like on blog posts, blog rolls etc. all the same data/use-cases that informed XFN.
image and name photo properties
Many proper noun references on web pages are simply an embedded image of that proper noun, typically a representative photo of the proper noun, often with its name as alt text.
Thus if a microformat is on an image element (<img src>) with only a root class name and no properties, then the src of the element is parsed as the u-photo property of the microformat, and if present, the alt of the element is parsed as the p-name property of the microformat.
Markup example:
<img class="h-card" src="http://example.org/pic.jpg" alt="Chris Messina" />
Parsed JSON:
{
"type": ["h-card"],
"properties": {
"name": ["Chris Messina"],
"photo": ["http://example.org/pic.jpg"]
}
}
to-do:
- try examples with organizations, events, products
use-cases:
- nearly every social networking site that shows a grid of people without text already does so with img tags and their names in the alt attribute. Most of those are linked too, which brings us to the next markup structure which implies properties:
hyperlinked image and name photo url properties
Often proper noun references on web pages are a representative image of the proper noun that is hyperlinked to a page about that proper noun.
Thus if a microformat is on a hyperlink element with only a root class name and no properties, and that element has but one child element that is an image, then in addition to implying the the URL from its href, the src of the child image element is parsed as the u-photo property of the microformat, and if present, its alt attribute is parsed as the p-name property of the microformat.
Markup example:
<a class="h-card" href="http://rohit.khare.org/">
<img alt="Rohit Khare"
src="https://s3.amazonaws.com/twitter_production/profile_images/53307499/180px-Rohit-sq_bigger.jpg" />
</a>
Parsed JSON:
{
"type": ["h-card"],
"properties": {
"name": ["Rohit Khare"],
"url": ["http://rohit.khare.org"],
"photo": ["https://s3.amazonaws.com/twitter_production/profile_images/53307499/180px-Rohit-sq_bigger.jpg"]
}
}
to-do:
- try examples with organizations, events, products
use-cases:
- nearly every social networking site that shows a grid of people without text already does so with hyperlinked img tags and their names in the alt attribute.
additional markup patterns to consider
Let's consider root class only on:
<abbr title>- implyp-namefromtitle<a href><abbr title>- implyu-urlfromhrefand implyp-namefrom the abbr element'stitle<object type="image/..." data="...">- implyu-photofromdataandp-namefrom text contents as with elements in general.<a href><object type="image/..." data="...">- implyu-urlfromhrefand implyu-photofrom the object element'sdataandp-namefrom text contents as with elements in general.
Can we document some use-cases, e.g. from Wikipedia?
rejected root only markup patterns
Is there anything that should be implied semantically from root class only on:
<audio src>- no, because there is no common practice of simple audio element usage for proper nouns, it's nearly always nested in a broader context.<time datetime>- no, because there are no microformats that are just a datetime<video src>- no, because there is no common practice of simple video element usage, it's nearly always nested in a broader context.
Use-case counter-examples welcome.