URL

The Open Graph protocol enables any web page to become a rich object in a social graph. For instance, this is used on Facebook to allow any web page to have the same functionality as any other object on Facebook. While many different technologies and schemas exist and could be combined together, there isn't a single technology which provides enough information to richly represent any web page within the social graph. The Open Graph protocol builds on these existing technologies and gives developers one thing to implement. Developer simplicity is a key goal of the Open Graph protocol which has informed many of the technical design decisions . 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 tags in the of your web page. The four required properties for every page are: 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 : . If a tag can have multiple values, just put multiple versions of the same tag on your page. The first tag (from top to bottom) is given preference during conflicts. 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. means there are 3 images on this page, the first image is 300x300 , the middle one has unspecified dimensions, and the last one is 1000 px tall. 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: 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 namespaced types which always have colons in them. 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:actor:role video:director video:writer video:duration video:release date video:tag video:series - video.tv show Which series this episode belongs to. These are globally defined objects that just don't fit into a vertical but yet are broadly used and agreed upon. 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: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. payment:description - string Description about the payment link. payment:currency - string The currency code ISO 4217 of the payment. payment:amount - float An amount requested on the payment link in decimal format. payment:expires at - datetime The date and time including minutes and seconds on which the payment link expires. payment:status - enum (PENDING, PAID, FAILED, EXPIRED) - Status of the payment. payment:id - string The unique identifier associated with the payment link for a given payment gateway or service provider. payment:success url - url A valid URL that gets redirected when payment is success. No additional properties other than the basic ones. Any non-marked up webpage should be treated as og:type website. The

We are committed to providing a friendly, safe, and welcoming environment for all. Please read and respect the Code of Conduct. Folks notice minor and larger issues with the URL Standard all the time and we'd love your help fixing those. Pull requests for typographical and grammar errors are also most welcome. Issues labeled "good first issue" are a good place to get a taste for editing the URL Standard. Note that we don't assign issues and there's no reason to ask for availability either, just provide a pull request. If you are thinking of suggesting a new feature, read through the FAQ and Working Mode documents to get yourself familiarized with the process. In short, change url.bs and submit your patch, with a good commit message. Please add your name to the Acknowledgments section in your first pull request, even for trivial fixes. The names are sorted lexicographically. To ensure your patch meets all the necessary requirements, please also see the Contributor Guidelines. Editors of the URL Standard are expected to follow the Maintainer Guidelines. A dashboard showing the tests running against browser engines can be seen at wpt.fyi/results/url. For quick local iteration, run make ; this will use a web service to build the standard, so that you don't have to install anything. See more in the Contributor Guidelines. Do not use newlines inside "inline" elements, even if that means exceeding the column width requirement. Using newlines between "inline" element tag names and their content is also forbidden. (This actually alters the content, by adding spaces.) That is Do not indent for anything except a new "block" element. For instance End tags may be included (if done consistently) and attributes may be quoted (using double quotes), though the prevalent theme is to omit end tags and not quote attributes (unless they contain a space). Place one newline between paragraphs (including list elements). Place three newlines before , and two newlines before other headings. This does not apply when a nested heading follows the parent heading. Use camel-case for variable names and "spaced" names for definitions, algorithms, etc. A complete JavaScript implementation of the standard can be found at jsdom/whatwg-url. This implementation is kept synchronized with the standard and tests. A complete Python implementation of the standard can be found at pywhatwgurl/pywhatwgurl. This implementation is kept synchronized with the standard and tests.