[Standards-JIG] UPDATED: JEP-0171 (Language Translation)

Peter Saint-Andre stpeter at jabber.org
Tue Apr 25 16:43:54 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jay Carlson wrote:
> Looks good to me.  (It's after midnight, we'll see what the reaction is from
> the implementers in the morning :-) 
> 
> I still owe the list some kind of alternative proposal for discovery of
> translation services.  For better or worse, I've been stuck in a parallel
> internal debate about how to describe and provide translation services over
> RESTy HTTP.  This has been more pressing for me, as I've got multiple
> applications breathing down my collar.  I hope it will teach me more about
> the right way to present this service over XMPP.

The fact that over XMPP you discover translation services using JEP-0030
(Service Discovery) does not mean that you can't discover them in other
ways using other protocols. So even if discovering translation services
via JEP-0030 is a SHOULD or MUST in XMPP band, that's what I call a
hypothetical imperative: if you discover via XMPP, you MUST use JEP-0030
(but if you discover outside the XMPP band, use some other mechanisms
that are defined elsewhere).

> If we feel that supporting automated discovery is a MAY rather than a
> SHOULD, we can start planning for interop testing now.  ORF in July?

The interop testing planned for July will cover RFCs 3920 and 3921 only
(plus, perhaps, JEP-0030).

Peter


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFETlHKNF1RSzyt3NURAoUTAJ9Xc1sLozl6ylzUGawq746ORQmNIQCgu/zA
gm5CTdoIGsA4V8FC2KSAlSI=
=KHOE
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060425/ecef98de/attachment.bin>


More information about the Standards mailing list