"rel" attribute of Lifecycle Event

[Kazuyoshi Kato]

Hi all,

I'm implementing an OpenSocial container with "Lifecycle Events".
But I found a little inconsistency in the spec.

In the OpenSocial spec. "rel" attribute of Link element is
"opensocialevent.TYPE".

http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/OpenSocial-Specification.html#rfc.section.4.1.7
> If the rel attribute is "opensocialevent", then all events are sent to
> that endpoint. If the rel attribute matches "opensocialevent.TYPE",
> then events of TYPE are sent to that endpoint.

But the below example is "event.TYPE".
> <Link rel="event" href="http://www.example.com/pingme" method="POST/>

This inconsistency is reported at 2008, but not fixed yet :(
http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/848c8d552e148964/48a391da576aecf1

In this thread, the attribute is "event.TYPE".
http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/7a8585eb6b04a574/b08aa53595a97a25

I don't know which is correct. Please clarify this. Thanks.

[Lane LiaBraaten]

I prefer "event".   Anyone else have an opinion?

-Lane

--

You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
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=.

[Kazuyoshi Kato]

On Fri, Nov 20, 2009 at 10:41 AM, Lane LiaBraaten <llia...@google.com> wrote:
> I prefer "event". Anyone else have an opinion?
> -Lane
>

Thanks!

And I can't find "opensocialevent" at the current draft of new spec :)
http://code.google.com/p/opensocial-resources/source/browse/spec/draft/OpenSocial-Gadget-XML.xml

However "event" is not reserved prefix yet.
http://code.google.com/p/opensocial-resources/source/browse/spec/draft/OpenSocial-Gadget-XML.xml#747

[Chris Chabot]

+1 to event, keeping it simple and all that :)

[Mark W.]

One thing that we are working on in 1.1 is adding pub/sub to gadgets.
http://wiki.opensocial.org/index.php?title=Incorporate_Open_Ajax_Hub_as_Pub-Sub_Mechanism_for_OpenSocial_1.next

I know these are different "events" but it would be good if we could
make sure that we don't introduce confusion by overloading the term
"event". Because of this, I'd prefer opensocialevent. This would let
gadgets pub/sub do "event".

As an aside, would you consider contributing an example of this to
Shindig? I think the lifecycle events are very powerful and we don't
do enough to show them as a key differentiator in OpenSocial.

-Mark W.




On Nov 20, 1:03 am, Kazuyoshi Kato <kato.kazuyo...@gmail.com> wrote:

> On Fri, Nov 20, 2009 at 10:41 AM, Lane LiaBraaten <lliab...@google.com> wrote:
> > I prefer "event".   Anyone else have an opinion?
> > -Lane
>
> Thanks!
>

> And I can't find "opensocialevent" at the current draft of new spec :)http://code.google.com/p/opensocial-resources/source/browse/spec/draf...
>
> However "event" is not reserved prefix yet.http://code.google.com/p/opensocial-resources/source/browse/spec/draf...

[Yoichiro Tanaka]

I think that we should use "event" for the lifecycle event. Because,
it is an event regarding Gadget, the Link tag is written in Gadget XML
file. In addition, it seems that the prefix "opensocial" looks wordy,
and the lifecycle event will be also used as a simple Gadget not
included OpenSocial.

Gadgets pub/sub is a specific function in OpenSocial, I think...
Therefore, I'd prefer "pubsub.event" or "pubsub" for the gadgets
pub/sub.

-Yoichiro

> --
>
> You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
> 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=.
>
>
>

--
Yoichiro Tanaka
Email: yoic...@eisbahn.jp
Blog: http://www.eisbahn.jp/yoichiro

[Mark W.]

Yoichiro,

I think your question has raised several interesting points....

The first is that there are likely to be several different kinds of
"events" when we are working with gadgets (social or otherwise). For
example, there are events that the gadget fires. These could be things
that are application specific, or things that ultimately get defined
in the spec as pub/sub becomes more prevalent. For example, it's not
unlikely that we would want a gadget to fire an event when it's view
changes. User prefs would be another area where events could be fired
when there are changes. I could also see the situation where, when we
are using social constructs, the gadget would like to indicate this
information as well. Changing the owner would be an example.

However, these seem very different from the kind of "event" that we
are talking about here. The difference is that these leave the
container and get sent to the gadget's host. What's defined as "life
cycle events" are more of a "call back" mechanism than a gadget-to-
gadget "event". For example, the scenario that we should enable is
that there is a "life cycle callback" that takes place as defined,
and, if the container supports pub/sub, a corresponding "life cycle
event" gets published. In this manner, the hosting server gets
notified that their application has been added/removed by a user, and,
in the browser, the container has the ability to let the other gadgets
know that this has happened.

If we were to change this, I think we should do two things:
The first is that we should avoid confusion with gadget-to-gadget
events, and name these something else, e.g. "Lifecycle Callbacks".
The second is that we should prefix gadget-to-gadget events with the
feature that defines them. For example, we'd have gadgets.prefs,
gadgets.views, or opensocial.owner.changed, et...

-Mark W.

On Nov 20, 9:12 pm, Yoichiro Tanaka <yoich...@eisbahn.jp> wrote:
> I think that we should use "event" for the lifecycle event. Because,
> it is an event regarding Gadget, the Link tag is written in Gadget XML
> file. In addition, it seems that the prefix "opensocial" looks wordy,
> and the lifecycle event will be also used as a simple Gadget not
> included OpenSocial.
>
> Gadgets pub/sub is a specific function in OpenSocial, I think...
> Therefore, I'd prefer "pubsub.event" or "pubsub" for the gadgets
> pub/sub.
>
> -Yoichiro
>
>
>
>
>
> On Sat, Nov 21, 2009 at 1:51 AM, Mark W. <weitz...@us.ibm.com> wrote:
> > One thing that we are working on in 1.1 is adding pub/sub to gadgets.

> >http://wiki.opensocial.org/index.php?title=Incorporate_Open_Ajax_Hub_...

>
> > I know these are different "events" but it would be good if we could
> > make sure that we don't introduce confusion by overloading the term
> > "event". Because of this, I'd prefer opensocialevent. This would let
> > gadgets pub/sub do "event".
>
> > As an aside, would you consider contributing an example of this to
> > Shindig? I think the lifecycle events are very powerful and we don't
> > do enough to show them as a key differentiator in OpenSocial.
>
> > -Mark W.
>
> > On Nov 20, 1:03 am, Kazuyoshi Kato <kato.kazuyo...@gmail.com> wrote:
> >> On Fri, Nov 20, 2009 at 10:41 AM, Lane LiaBraaten <lliab...@google.com> wrote:
> >> > I prefer "event".   Anyone else have an opinion?
> >> > -Lane
>
> >> Thanks!
>
> >> And I can't find "opensocialevent" at the current draft of new spec :)http://code.google.com/p/opensocial-resources/source/browse/spec/draf...
>
> >> However "event" is not reserved prefix yet.http://code.google.com/p/opensocial-resources/source/browse/spec/draf...
>
> > --
>
> > You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
> > 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 athttp://groups.google.com/group/opensocial-and-gadgets-spec?hl=.
>
> --
> Yoichiro Tanaka
> Email: yoich...@eisbahn.jp
> Blog:http://www.eisbahn.jp/yoichiro

[Kazuyoshi Kato]

On Sat, Nov 21, 2009 at 1:51 AM, Mark W. <weit...@us.ibm.com> wrote:
> One thing that we are working on in 1.1 is adding pub/sub to gadgets.
> http://wiki.opensocial.org/index.php?title=Incorporate_Open_Ajax_Hub_as_Pub-Sub_Mechanism_for_OpenSocial_1.next
>
> I know these are different "events" but it would be good if we could
> make sure that we don't introduce confusion by overloading the term
> "event". Because of this, I'd prefer opensocialevent. This would let
> gadgets pub/sub do "event".

I think "opensocialevent" can't solve the confusion.
Because Lifecycle Events and pubsub are both part of OpenSocial.

> As an aside, would you consider contributing an example of this to
> Shindig? I think the lifecycle events are very powerful and we don't
> do enough to show them as a key differentiator in OpenSocial.

Sorry, our company's implementation is written in Perl.
# And Yoichiro is my boss :)

However, It's interesting idea. I wanna try it as a my personal project.

[yoichiro]

Mark,

> The first is that we should avoid confusion with gadget-to-gadget
> events, and name these something else, e.g. "Lifecycle Callbacks".

No, as the current spec, events of a gadget should be called "Life
cycle event". The thing to be called back is the result, not be a
purpose. The purpose is a handling events regarding the gadget. The
callback is the one of them.

Also, how do you think if there is SNS that has already adopted the
current specification? I think that your idea is not realistic.

As an aside, the unit of the pub/sub model should be called "topic",
not be called "event", right?

-Yoicihro