20
The Open Graph protocol Understanding the design decisions WWW Conference April th, David Recordon

The Open Graph Protocol Design Decisions

Embed Size (px)

DESCRIPTION

Presentation at the W3C's Linked Data Camp at WWW 2010. April 29th, 2010.

Citation preview

Page 1: The Open Graph Protocol Design Decisions

The Open Graph protocolUnderstanding the design decisions

WWW Conference !"#"April !$th, !"#"David Recordon

Page 2: The Open Graph Protocol Design Decisions

The product experience

Page 3: The Open Graph Protocol Design Decisions

Design goals

Page 4: The Open Graph Protocol Design Decisions

Useful to others beyond Facebook.

Page 5: The Open Graph Protocol Design Decisions

Copy and paste.

Page 6: The Open Graph Protocol Design Decisions

Simple markup. Simple schema.

Page 7: The Open Graph Protocol Design Decisions

What’s needed?

Page 8: The Open Graph Protocol Design Decisions

! What is the user liking?

" A clean page title

# An image

$ A canonical URL

Page 9: The Open Graph Protocol Design Decisions

!) What is the user likingBased off of the most popular categories for Facebook Pages.

▪ Activities

▪ Businesses

▪ Groups

▪ Organizations

▪ People

▪ Places

▪ Products and Entertainment

▪ Websites

Page 10: The Open Graph Protocol Design Decisions

") A clean page titleSearch Engine Optimization has caused all sorts of stuff to be crammed into the <title> tag.

▪ “The Semantic Web & THE POWER OF PULL | Blog Archive | The Facebook Open Graph, Part I”

▪ “A New Data Model –%Facebook Developer Blog”

▪ “W&C Track @ WWW!"#", Raleigh, NC, USA ; !$-&" April !"#"”

▪ “Open Graph Protocol | Google Groups”

Page 11: The Open Graph Protocol Design Decisions

#) A canonical URLWe wanted to use link-rel canonical.

▪ Major publishers were concerned that adding link-rel canonical would negatively impact their ranking within search engines.

Page 12: The Open Graph Protocol Design Decisions

A simple example

Page 13: The Open Graph Protocol Design Decisions

What’s desired?

Page 14: The Open Graph Protocol Design Decisions

% A short description

& A site name (for collections of pages)

' Location information

( Contact information

Page 15: The Open Graph Protocol Design Decisions

$) A short descriptionA simple schema.

▪ Not respecting Don’t Repeat Yourself.

▪ Optimized for a consistent schema versus reuse of existing meta tags.

▪ One namespace. One prefix.▪ One HTML tag attribute (“property”)

Page 16: The Open Graph Protocol Design Decisions

What we didn’t wantBut tried.

Too complex!

Page 17: The Open Graph Protocol Design Decisions

%) Location information

▪ Couldn’t find a – simple – location markup specification.

▪ Reused the property names from the Microformat hCard

▪ Fully expect this information to be expressed within the page body versus the head.

▪ RDFa gives us a consistent syntax for both cases.

Page 18: The Open Graph Protocol Design Decisions

Adoption

Page 19: The Open Graph Protocol Design Decisions

AdoptionSeven days later!

▪ Hosted services

▪ og:it - simple metadata extractor to HTML▪ OpenGraph.in - simple metadata extractor to HTML and JSON▪ Multiple RDF parsers now understand the Open Graph protocol▪ Open Graph protocol to JSON convertor for testing

▪ Open Source libraries for Java, Perl, PHP, and Ruby

▪ WordPress plugin for easy publishing

http://opengraphprotocol.org/#implementations