OpenSocial Extensions section in OpenSocial-Specification.xml

This is the first pass at the extensions section. It has the basic structure and the start of some content. Put in here so people can get a sense of where I'm going for either confirmation and an early course corrections

[Lane LiaBraaten, 2009-11-17 18:29:12]

hmmm...the side-by-side diff isn't working.  Can you try to upload another patch
set?

[Lane LiaBraaten, 2009-11-17 18:35:52]

Overall, looking good.

Responding to some of your question 'Should we limit the namespace?'
Yes, extensions should not use the gadgets, opensocial, osapi, os, etc
namespaces.  This is so that developers using the features know that they're
using an experimental feature. Maybe we even want to RECOMMEND something about
the namespace to use (e.g. opensocialx, osapix, osx)?

I like including the .incubating on feature names (e.g.<Require
feature="pub-sub.incubating">).  These features should still use a version
number though.

Looks like there's a fair amount of spec formatting to add.  Let me know when
you have a patch with more XML tags and I can add it to the preview I started
today.

Cheers,
Lane

[Mark W., 2009-11-18 04:54:02]

Here's another rev of the doc. More content in the sections and, hopefully, some
formatting.

[Mark W., 2009-11-18 04:54:38]

Prototype of extensions. Apply to shindig beta 5. run in sample container.

[Mark W., 2009-11-18 17:24:39]

Added some examples to the extensions section.

[Mark W., 2009-11-18 17:25:12]

Corresponding prototype patch illustrating examples.

[Mark W., 2009-11-18 20:40:14]

Updated prototype. Apply this to shindig. Includes an examples gadget.

[Lane LiaBraaten, 2009-11-23 18:44:14]

On 2009/11/18 20:40:14, weitzelm.ibm wrote:
> Updated prototype. Apply this to shindig. Includes an examples gadget.

I still can't view the side by side diff for the spec.

Can you separate it from the shindig patch?

[Lane LiaBraaten, 2009-11-24 16:57:58]

There is a upload.py script you can get from codereview site.  Running that
from within your svn dir will create a new issue based on your current
chnages.

You can also just run 'svn diff > my.patch' and upload my.patch to the code
review site.

On Nov 24, 2009 6:00 AM, "Mark Weitzel" <weitzelm.ibm@gmail.com> wrote:

OK... Not sure what the deal is, but I've attached the file.
How are you making the patch that you submit to the code review tool? I'm
using Eclipse to do this. Although we've never had problems in the past with
Apache stuff, maybe it's doing something funky here.

Let me know.

Also, I'd like to talk through the extending protocol idea after you've had
a chance to look over the text and example.

-Mark W.

On Mon, Nov 23, 2009 at 1:44 PM, <lliabraa@google.com> wrote: > > On
2009/11/18 20:40:14, weitzelm...