[Members] Motion for Last Call on JEP 88
richard at dobson-i.net
Fri Mar 12 11:08:18 CST 2004
>> One of my main beefs with JEP-0088 is that it should be
>> Informational rather than Standards Track.
>I can see a use for the concept of embedding webpages into clients, and
>if this is something to be done from the server-side it will be pretty
>useless if we don't have standardization.. But this JEP is pretty bare.
>If it is going to be on the Standards track I think it needs a lot more
>meat in it. For example:
If you have any suggestions of which parts I can "beef up" feel free, ive
submitted this for last call now as the last time I brought up this JEP only
a few suggestions for change were made which I did so.
>1) Some of the language was a bit ambiguous to me. I'd like to see the
>Terminaology stuff inserted that most other JEPs contain now (e.g. "The
>keywords "MUST", "MUST NOT"...).
Which parts are ambiguious?
>2) What kind of data are we expecting from the webtab component? How
>will it be transmitted? I would _assume_ that the webtab component is
>meant to be simply a webserver with a small XMPP piece to point jabber
>clients to one or more URLs located on that webserver. But is the
>Jabber client expected then to switch to HTTP and display that URL
>inside a "webtab"? That's more or less how I understand Yahoo et. al.
>to do it but that does not mean that's how Jabber clients should do it.
>Again, I am just assuming here.
It is simply a way of letting the client know about web pages/web
applications that are designed for webtab use that are available from that
Jabber Server provider. All you need to do in the client is fire up and
embedded web browser and in my case in my client I use the Webrowser control
on windows embedded into a dialog (exactly the same way as Yahoo do it, and
MSN messenger does it). The webtab component is either embedded into the
jabber server or is a separate component (as shown in the JEP) and is
completely separate from the actual webserver that serves the webtab pages,
there need not be any tie in inbetween these two components.
How would you suggest I alter the text in the JEP to make this clearer to
>3) Alternatively, will the data to be displayed be encapsulated within
>XML stanzas? If so the JEP would seem to be dependent on something like
>XHTML-IM, right? Can't very well move forward with this JEP without
>that one too.
No that is not how it is intended to work.
>4) Type. "The "type" is a hint to the client of what the service being
>provided is, this allows a client to possibly display icons on the tabs
>to represent them". Why be so vague? Let's define a small number of
>them (you have a beginning there in the example code) and write a short
>description for each. That will aid implementations and perhaps
>generate some more interest as well.
I did write an example list of them at the bottom (where I thought was
appropriate in "Jabber Registrar Considerations "), and included
More information about the Members