Discussions - OpenSocial and Gadgets Specification Discussion

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 »

By Arne Roomann-Kurrik - Sep 16 - 5 new of 5 messages

	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 By Robert Koberg - Nov 6 - 4 new of 4 messages

	What do you use for editing the specifications?
	Are we all just using text editors, or are there some tools? By Jon - Nov 6 - 2 new of 2 messages

	Separation of Gadgets and OpenSocial (Option 2)
	[link] File draft/Gadgets-API-Specificatio n.xml (left): [link] Line 574: <t>sign_owner: gadgets.io.RequestParameters.S IGN_OWNER (default 'true')</t> See the comment in the OpenSocial specification on the Views. We can... more » By jon.weyga...@gmail.com - Nov 4 - 3 new of 3 messages

	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 » By Lane LiaBraaten - Nov 4 - 7 new of 7 messages

	Proposal for 1.0 - Support authenticated iframe mode "type=URL" application
	Knowing it might be a bit late, but I'm just wondering whether it's possible to add the proposal "Support authenticated iframe mode "type=URL" application" into v1.0 spec? The detailed proposal could be find here: [link] It could benefit developers a lot if the gadget's behavior matches:... more » By 王超 Jacky Wang - Nov 4 - 8 new of 8 messages

	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 » By api.lliab...@gmail.com - Nov 3 - 1 new of 1 message

	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 » By Jon - Nov 2 - 21 new of 21 messages

	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 » By Lev Epshteyn - Nov 2 - 9 new of 9 messages

	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 » By Lane LiaBraaten - Nov 2 - 4 new of 4 messages

	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 » By lliab...@google.com - Nov 2 - 1 new of 1 message