Movatterモバイル変換


[0]ホーム

URL:


The Open Graph protocol

Open Graph protocol logo

Introduction

TheOpen Graph protocol enables any web page to become arich object in a social graph. For instance, this is used on Facebook to allowany web page to have the same functionality as any other object on Facebook.

While many different technologies and schemas exist and could be combinedtogether, there isn't a single technology which provides enough information torichly represent any web page within the social graph. The Open Graph protocolbuilds on these existing technologies and gives developers one thing toimplement. Developer simplicity is a key goal of the Open Graph protocol whichhas informed many ofthe technical design decisions.


Basic Metadata

To turn your web pages into graph objects, you need to add basic metadata toyour page. We've based the initial version of the protocol onRDFa which means that you'll placeadditional<meta> tags in the<head> of your web page. The four requiredproperties for every page are:

As an example, the following is the Open Graph protocol markup forThe Rock onIMDB:

<html prefix="og: https://ogp.me/ns#"><head><title>The Rock (1996)</title><meta property="og:title" content="The Rock" /><meta property="og:type" content="video.movie" /><meta property="og:url" content="https://www.imdb.com/title/tt0117500/" /><meta property="og:image" content="https://ia.media-imdb.com/images/rock.jpg" />...</head>...</html>

Optional Metadata

The following properties are optional for any object and are generallyrecommended:

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

<meta property="og:audio" content="https://example.com/bond/theme.mp3" /><meta property="og:description"   content="Sean Connery found fame and fortune as the           suave, sophisticated British agent, James Bond." /><meta property="og:determiner" content="the" /><meta property="og:locale" content="en_GB" /><meta property="og:locale:alternate" content="fr_FR" /><meta property="og:locale:alternate" content="es_ES" /><meta property="og:site_name" content="IMDb" /><meta property="og:video" content="https://example.com/bond/trailer.swf" />

The RDF schema (inTurtle) can be found atogp.me/ns.


Structured Properties

Some properties can have extra metadata attached to them.These are specified in the same way as other metadata withproperty andcontent, but theproperty will have extra:.

Theog:image property has some optional structured properties:

A full image example:

<meta property="og:image" content="http://example.com/ogp.jpg" /><meta property="og:image:secure_url" content="https://secure.example.com/ogp.jpg" /><meta property="og:image:type" content="image/jpeg" /><meta property="og:image:width" content="400" /><meta property="og:image:height" content="300" /><meta property="og:image:alt" content="A shiny red apple with a bite taken out" />

Theog:video tag has the identical tags asog:image. Here is an example:

<meta property="og:video" content="http://example.com/movie.swf" /><meta property="og:video:secure_url" content="https://secure.example.com/movie.swf" /><meta property="og:video:type" content="application/x-shockwave-flash" /><meta property="og:video:width" content="400" /><meta property="og:video:height" content="300" />

Theog:audio tag only has the first 3 properties available(since size doesn't make sense for sound):

<meta property="og:audio" content="http://example.com/sound.mp3" /><meta property="og:audio:secure_url" content="https://secure.example.com/sound.mp3" /><meta property="og:audio:type" content="audio/mpeg" />

Arrays

If a tag can have multiple values, just put multiple versions of the same<meta> tag on your page. The first tag (from top to bottom) is givenpreference during conflicts.

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

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

For example:

<meta property="og:image" content="https://example.com/rock.jpg" /><meta property="og:image:width" content="300" /><meta property="og:image:height" content="300" /><meta property="og:image" content="https://example.com/rock2.jpg" /><meta property="og:image" content="https://example.com/rock3.jpg" /><meta property="og:image:height" content="1000" />

means there are 3 images on this page, the first image is300x300, the middleone has unspecified dimensions, and the last one is1000px tall.


Object Types

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

<meta property="og:type" content="website" />

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

<head prefix="my_namespace: https://example.com/ns#"><meta property="og:type" content="my_namespace:my_type" />

The global types are grouped into verticals. Each vertical has itsown namespace. Theog:type values for a namespace are always prefixed withthe namespace and then a period.This is to reduce confusion with user-defined namespaced types which alwayshave colons in them.

Music

og:type values:

music.song

music.album

music.playlist

music.radio_station

Video

og:type values:

video.movie

video.episode

video.tv_show

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

video.other

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

No Vertical

These are globally defined objects that just don't fit into a vertical butyet are broadly used and agreed upon.

og:type values:

article - Namespace URI:https://ogp.me/ns/article#

book - Namespace URI:https://ogp.me/ns/book#

payment.link - Namespace URI:https://ogp.me/ns/payment# 🚧Beta only

profile - Namespace URI:http://ogp.me/ns/profile#

website - Namespace URI:https://ogp.me/ns/website#

No additional properties other than the basic ones.Any non-marked up webpage should be treated asog:type website.


Types

The following types are used when defining attributes in Open Graph protocol.

TypeDescriptionLiterals
BooleanA Boolean represents a true or false valuetrue, false, 1, 0
DateTimeA DateTime represents a temporal value composed of a date (year, month, day) and an optional time component (hours, minutes)ISO 8601
EnumA type consisting of bounded set of constant string values (enumeration members).A string value that is a member of the enumeration
FloatA 64-bit signed floating point numberAll literals that conform to the following formats:

1.234
-1.234
1.2e3
-1.2e3
7E-10
IntegerA 32-bit signed integer. In many languages integers over 32-bits become floats, so we limit Open Graph protocol for easy multi-language use.All literals that conform to the following formats:

1234
-123
StringA sequence of Unicode charactersAll literals composed of Unicode characters with no escape characters
URLA sequence of Unicode characters that identify an Internet resource.All valid URLs that utilize the http:// or https:// protocols

Implementations

The open source community has developed a number of parsers and publishingtools. Let the Facebook group know if you've built something awesome too!


The Open Graph protocol was originally created at Facebook and is inspired byDublin Core,link-rel canonical,Microformats, andRDFa. The specification described on this page is available under theOpen Web Foundation Agreement, Version 0.9. This website isOpen Source.


[8]ページ先頭

©2009-2026 Movatter.jp