What is The Open Graph protocol?

The Open Graph protocol enables any web page to become a rich object in a social graph. For example, this is used on Facebook to allow any web page to have the same functionality as any other object on Facebook.

Metadata – The Open Graph Protocol

To turn your web pages into graph objects, you need to add basic metadata to your page. We’ve based the initial version of the protocol on RDFa which means that you’ll place additional <meta> tags in the <head> of your web page. The four required properties for every page are:

  • og:title – The title of your object as it should appear within the graph, e.g., “The Movie”.
  • og:type – The type of your object, e.g., “video.movie”. Depending on the type you specify, other properties may also be required.
  • og:image – An image URL which should represent your object within the graph.
  • og:url – The canonical URL of your object that will be used as its permanent ID in the graph, e.g., “http://www.imdb.com/title/tt0117500/”.

As an example, the following is the Open Graph protocol markup for The Rock on IMDB:

 

Structured Properties

Some properties can have extra metadata attached to them. These are specified in the same way as other metadata with property and content, but the property will have extra :.

The og:image property has some optional structured properties:

  • og:image:url – Identical to og:image.
  • og:image:secure_url – An alternate url to use if the webpage requires HTTPS.
  • og:image:type – A MIME type for this image.
  • og:image:width – The number of pixels wide.
  • og:image:height – The number of pixels high.
  • og:image:alt – A description of what is in the image (not a caption). If the page specifies an og:image it should specify
  • og:image:alt.

Full Image Example:

Optional Metadata

The following properties are optional for any object and are generally recommended:

  • og:audio – A URL to an audio file to accompany this object.
  • og:description – A one to two sentence description of your object.
  • og:determiner – The word that appears before this object’s title in a sentence. An enum of (a, an, the, “”, auto). If auto is chosen, the consumer of your data should chose between “a” or “an”. Default is “” (blank).
  • og:locale – The locale these tags are marked up in. Of the format language_TERRITORY. Default is en_US.
  • og:locale:alternate – An array of other locales this page is available in.
  • og:site_name – If your object is part of a larger web site, the name which should be displayed for the overall site. e.g., “IMDb”.
  • og:video – A URL to a video file that complements this object.

For example (line-break solely for display purposes):

The RDF schema (in Turtle) can be found at ogp.me/ns.

Structured Properties

Some properties can have extra metadata attached to them. These are specified in the same way as other metadata with property and content, but the property will have extra :.

The og:image property has some optional structured properties:

  • og:image:url – Identical to og:image.
  • og:image:secure_url – An alternate url to use if the webpage requires HTTPS.
  • og:image:type – A MIME type for this image.
  • og:image:width – The number of pixels wide.
  • og:image:height – The number of pixels high.
  • og:image:alt – A description of what is in the image (not a caption). If the page specifies an og:image it should specify og:image:alt.

Structured Data

Arrays

If a tag can have multiple values, just put multiple versions of the sametag on your page. The first tag (from top to bottom) is given preference during conflicts.

<meta property="og:image" content="http://example.com/rock.jpg" />

 

Put structured properties after you declare their root tag. Whenever another root element is parsed, that structured property is considered to be done and another one is started.

For example:
Arrays - Open Graph Protocol

This means there are 3 images on this page, the first image is 300×300, the middle one has unspecified dimensions, and the last one is 1000px tall.

Object Types

In order for your object to be represented within the graph, you need to specify its type. This is done using the og:type property:

When the community agrees on the schema for a type, it is added to the list of global types. All other objects in the type system are CURIEs of the form.

The global types are grouped into verticals. Each vertical has its own namespace. The og:type values for a namespace are always prefixed with the namespace and then a period. This is to reduce confusion with user-defined name-spaced types which always have colons in them.

Music

  • Namespace URI: http://ogp.me/ns/music#

og:type values:

music.song
  • music:duration – integer >=1 – The song’s length in seconds.
  • music:album – music.album array – The album this song is from.
  • music:album:disc – integer >=1 – Which disc of the album this song is on.
  • music:album:track – integer >=1 – Which track this song is.
  • music:musician – profile array – The musician that made this song.
music.album
  • music:song – music.song – The song on this album.
  • music:song:disc – integer >=1 – The same as music:album:disc but in reverse.
  • music:song:track – integer >=1 – The same as music:album:track but in reverse.
  • music:musician – profile – The musician that made this song.
  • music:release_date – datetime – The date the album was released.
music.playlist
  • music:song – Identical to the ones on music.album
  • music:song:disc
  • music:song:track
  • music:creator – profile – The creator of this playlist.
music.radio_station

music:creator – profile – The creator of this station.


Video

  • Namespace URI: http://ogp.me/ns/video#

og:type values:

video.movie

  • video:actor – profile array – Actors in the movie.
  • video:actor:role – string – The role they played.
  • video:director – profile array – Directors of the movie.
  • video:writer – profile array – Writers of the movie.
  • video:duration – integer >=1 – The movie’s length in seconds.
  • video:release_date – datetime – The date the movie was released.
  • video:tag – string array – Tag words associated with this movie.

video.episode

  • video:actor – Identical to video.movie
  • video:actor:role
  • video:director
  • video:writer
  • video:duration
  • video:release_date
  • video:tag
  • video:series – video.tv_show – Which series this episode belongs to.

video.tv_show

A multi-episode TV show. The metadata is identical to video.movie.

video.other

A video that doesn’t belong in any other category. The metadata is identical to video.movie.


No Vertical

These are globally defined objects that just don’t fit into a vertical but yet are broadly used and agreed upon.

og:type values:

Article – Namespace URI: http://ogp.me/ns/article#

  • article:published_time – datetime – When the article was first published.
  • article:modified_time – datetime – When the article was last changed.
  • article:expiration_time – datetime – When the article is out of date after.
  • article:author – profile array – Writers of the article.
  • article:section – string – A high-level section name. E.g. Technology
  • article:tag – string array – Tag words associated with this article.

Book – Namespace URI: http://ogp.me/ns/book#

  • book:author – profile array – Who wrote this book.
  • book:isbn – string – The ISBN
  • book:release_date – datetime – The date the book was released.
  • book:tag – string array – Tag words associated with this book.

Profile – Namespace URI: http://ogp.me/ns/profile#

  • profile:first_name – string – A name normally given to an individual by a parent or self-chosen.
  • profile:last_name – string – A name inherited from a family or marriage and by which the individual is commonly known.
  • profile:username – string – A short unique string to identify them.
  • profile:gender – enum(male, female) – Their gender.

Website – Namespace URI: http://ogp.me/ns/website#

 

Read More Guides from Omaha Code

Leave a Reply