[Standards-JIG] Re: UPDATED: JEP-0081 (Jabber MIME Type)

Peter Saint-Andre stpeter at jabber.org
Tue Jan 18 18:13:46 UTC 2005

Actually, I think it would be better to just include an XMPP URI in the 
application/jabber+xml file. 

So instead of this:

  <chat>stpeter at jabber.org</chat>

We would have:

<jabber>xmpp:stpeter at jabber.org?message&type=chat</jabber>

That way, we don't hard-code use cases into the schema, and you can 
support any use cases that can be encoded into an XMPP URI. Thus, the 
Jabber MIME type simply provides a way to get around bad browers and 
operating systems that make it prohibitively hard to add support for new 
URI schemes.



In article <41DE5099.4050404 at pandion.be>,
 Sebastiaan Deckers <cbas at pandion.be> wrote:

> Why were those use cases removed?  I think atleast the vcard command was 
> good.
> JEP Editor wrote:
> >Version 0.4 of JEP-0081 (Jabber MIME Type) has been released.
> >
> >Abstract: This JEP specifies a MIME type for launching a Jabber client as a 
> >helper application from most modern web browsers, and for completing basic 
> >use cases once the client is launched.
> >
> >Changelog: Reinstated the proposal since it fills a need not met by RFC 3923 
> >and draft-saintandre-xmpp-uri; specified XML schema; specified IANA 
> >considerations, including content-type registration; further specified 
> >security considerations; removed use cases for service discovery, directory 
> >search, vCard lookup, and authentication; added more detailed descriptive 
> >text to remaining use cases. (psa)
> >
> >URL: http://www.jabber.org/jeps/jep-0081.html
> >

More information about the Standards mailing list