Defining an OpenSocial microdata mapping in 3.0

[Matthew Marum]

I think we should look at defining a microdata mapping for OpenSocial data types.

Defining an OpenSocial microdata model would allow you to tag social content within a page for Search Engine Optimization, Reporting, OpenSocial "like" buttons, etc.

I also think there are use cases where you could put Gadget data / EE data within a page so 3rd parties can easily embed OpenSocial apps into their page.

What do people think about this?

Matt

[Ryan Baxter]

+1 Matt I agree. I think this has a lot of potential.

[Mark W.]

I also agree. I'd like to do this using some kind of path structure. This would allow us to simplify the action contribution model to use only paths.

[Andy Smith]

+1

On Tue, Feb 7, 2012 at 8:45 PM, Mark W. <weitze...@gmail.com> wrote:

I also agree. I'd like to do this using some kind of path structure. This would allow us to simplify the action contribution model to use only paths.

--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.

To view this discussion on the web visit https://groups.google.com/d/msg/opensocial-and-gadgets-spec/-/lmmcMTbvMasJ.

To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.

--
Thank you,

Andy

[Paul Lindner]

Just declare schema.org entities mapping to the functionality you want to provide.  Not sure why microdata should be opensocial specific.

Paul Lindner -- lin...@inuus.com -- profiles.google.com/pmlindner

[Matthew Marum]

That's definitely a possibility.  I haven't had a chance to look at this much yet.

Matt