[Council] namespaces as HTTP URIs

Thomas Muldowney temas at box5.net
Mon Oct 7 11:05:27 CDT 2002


I think the very recent JEPs should use this, such as MU-Chat, but I
don't think we need to force it on the slightly older ones that are
potentially already being played with in clients.  As to point 2, yes =)

--temas


On Mon, Oct 07, 2002 at 08:41:41AM -0500, Peter Saint-Andre wrote:
> The sense I got from our meeting the other night is that, going forward, 
> we would prefer all namespace declarations to be URIs (specifically HTTP
> URIs). So I'm thinking that anything we vote to Draft from now on must
> express namespaces as http://www.jabber.org/protocol/blah rather than
> jabber:*:* as we've done until now.
> 
> Two questions:
> 
> 1. Shall we enforce this on the JEPs that I will send to the Council soon
> (server-based privacy rules, feature negotiation, and multi-user chat)?
> 
> 2. Shall I add something about this to JEP-0001 and the JEP template?
> 
> My answer is yes to both, but I'd like to get consensus on this from the
> Council before proceeding.
> 
> Peter
> 
> --
> Peter Saint-Andre
> Jabber Software Foundation
> http://www.jabber.org/people/stpeter.php
> 
> _______________________________________________
> Council mailing list
> Council at jabber.org
> http://mailman.jabber.org/listinfo/council
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://jabber.org/pipermail/council/attachments/20021007/2d9aa320/attachment.pgp


More information about the Council mailing list