W3C home > Mailing lists > Public > public-html@w3.org > April 2010

RE: ISSUE-41: Facebook open graph protocol

From: Ennals, Robert <robert.ennals@intel.com>
Date: Fri, 23 Apr 2010 22:12:02 +0100
To: Philippe Le Hegaret <plh@w3.org>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <83D7DEC65EB438489DE261BD36F1F11F371F3BC4@irsmsx503.ger.corp.intel.com>
Of course, it's quite possible that whatever solution we agree on will allow xmlns in some form, and that form may have some degree of compatibility with what Facebook is deploying.

For example, I could see a reasonable argument for extending my "extensionslikesvg" change proposal to explicitly state that a conforming extension can use CURIEs in its attribute values, provided that all prefixes are fixed and registered, and also allow one to use xmlns to explicitly give the namespace for such a prefix. This would be similar to the approach that the proposal already takes to defining new attributes.


> -----Original Message-----
> From: public-html-request@w3.org [mailto:public-html-request@w3.org] On
> Behalf Of Philippe Le Hegaret
> Sent: Thursday, April 22, 2010 12:28 PM
> To: public-html@w3.org
> Subject: ISSUE-41: Facebook open graph protocol
> Facebook announced yesterday support for the open graph protocol [1].
> It
> allows website to integrate themselves into the facebook social graph.
> They already have several partners that are going to deploy that with
> them.
> Their system is based on RDFa, and thus using xmlns attributes:
> [[
> <html xmlns:og="http://opengraphprotocol.org/schema/"
>       xmlns:fb="http://developers.facebook.com/schema/">
>   <head>
>     <title>The Rock (1996)</title>
>     <meta property="og:title" content="The Rock" />
>     <meta property="og:type" content="movie" />
>     <meta property="og:url"
> content="http://www.imdb.com/title/tt0117500/ "/>
>     <meta property="og:image"
> content="http://ia.media-imdb.com/rock.jpg" />
> ]]
> They're using XHTML 1.0 with the media type text/html. I don't think
> they're going to switch to application/xhtml+xml soon.
> Effectively, from a technical perspective, it's a great news for the
> RDFa community. But, from the point of HTML, Facebook and their
> partners
> are deploying xmlns attributes in HTML all over the Web, independently
> of what the HTML5 specification is currently saying. So, that makes me
> wonder how relevant the HTML5 resolution on ISSUE-41 is going to be,
> Philippe
> [1]  http://developers.facebook.com/docs/opengraph
Received on Friday, 23 April 2010 21:12:44 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:01 UTC