Discussions > OpenSocial and Gadgets Specification Discussion
You cannot post messages because only members can post, and you are not currently a member.
|
READ FIRST - Messages are now moderated for new members
|
| |
I've noticed a couple of spam messages coming to this list and I'd
like to put a stop to it early. I've turned on post moderation for
new users.
If you're posting to this group for the first time, it may take a day
or two for your first messages to appear, because a human being will
have to look at what you wrote to make sure that you're not a... more »
|
|
ufff...
|
| |
Any chance of shortening '[opensocial-and-gadgets-spec] ' -- how about [osgs] ?
Do you skip a lot of messages because you don't want to make the effort to read the subject? (I do)
best,
-Rob
|
|
Revising the compliance section
|
| |
Hey Folks,
I've been doing some more thinking about how to revise the compliance
section, and I have a proposal that's ready for feedback on the wiki [1].
In short, the proposal defines the following four levels of compliance:
- *OpenSocial Container*
- meets Social Gadget Container criteria... more »
|
|
Deprecate redundant opensocial.* objects
|
| |
Reviewers: opensocial-and-gadgets-spec_go oglegroups.com,
Message:
I've moved the redundant method into a new file "OpenSocial Deprecated
JavaScript API", and added links to the osapi methods that replace them.
I captured a few issues here:
[link]... more »
|
|
Proposal for 1.0 - Clarify Separation of Gadgets (opensocial namespace)
|
| |
How to address the issues of "opensocial" name space where it is
really not specific to opensocial?
Some examples:
opensocial-i18n - feature name
opensocial_proxied_content - a needed flag for proxied content
opensocial_viewer_id, opensocial_owner_id - if we keep the generic
concepts of viewer and owner... more »
|
|
Proposal for 1.0 - <os:Var>
|
| |
Here are my comments on the proposal at
[link]
...
- Allowing both <os:Var key="a" value="${foo}"/> and <os:Var
key="a">${foo}</os:Var> seems redundant. Let's pick one. Which one depends
on the kinds of usages we want.... more »
|
|
Timeline update
|
| |
I'd like to update the timeline [1] to reflect reality. We're currently
slated to be done with spec patches on Nov 6, but that's not likely. I'd
like to set a fairly aggressive deadline for owners to formalize their
proposals into spec patches - I think it helps clarify the proposal and
foster discussion.... more »
|
|
Separation of Gadgets and OpenSocial (Option 2)
|
| |
In general, I'm not sure all of these changes are predicated on the
social vs. plain ol' gadgets distinction. For example, information
about the owner and viewer may be useful even in a non-social
environment.
[link]
File draft/Gadgets-API-Specificatio n.xml (left):... more »
|
|
|