From the introduction:
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.
The usual suspects, Google, Microsoft, Facebook, etc.
There are a number of open source parsing/publishing tools listed at this page.
Additional information about web pages and their contents would be very useful, if we could just get users to enter the information.
The Open Graph Database Protocol is yet another attempt to find the minimum users are willing to do.
But not by observing user behavior.
By deciding what is the minimum useful set of data and developing a way for users to enter it.
I am sure there will be users who will enter information and it will improve the pages where it used.
But, not every user will use it and most likely those that do, will use it inconsistently.
Open Graph Database Protocol will become another lingo to parse and track across the Web.
[…] O’Donnell replied to my tweet on a post about Open Graph Database Protocol, saying: @patrickDurusau re #opengraph thoughts how #topicmaps can be used as alternatives for […]
Pingback by Topic Maps as Alternative to Open Graph Database Protocol? « Another Word For It — November 22, 2011 @ 6:58 pm