[JDEV] Jabber protocol's use of XML Namespaces

[Thomas Muldowney]

Besides the reasoning of creating valid XML and allowing correct parsing of the XML elements that have the 
same name, there is a larger reason.

(Thanks Dave "DizzyD" Smith for wording this better than I could)
We use them for the same reason that you use multiple files in a software  project -- you group 
functionality into small, free-standing groups.   That way you can enhance a module without requiring a 
change to the entire project.  It also ensures that clients can support a minimal feature set without 
having to force client authors to define custom "subsets" of the protocol -- hence it discourages protocol 
version forking

--temas

On Thu, Aug 31, 2000 at 11:11:58AM -0700, Robert Temple wrote:
> It seems strange to me the way the jabber protocol uses XML namespaces.  It would have made a lot more sense to me if everything that is documented in the JPG was placed in one namespace and that anytime someone wanted to add something specific to their client/server, they could put that in their own namespace.
> 
> Its really bizarre that the jabber protocol actually has more namespaces specifications in it then it does element specifications.  IMHO, namespaces should have been used simply as a means to extend the protocol and to specify optional elements.
> 
> What is gained by having:
> <iq type="set" id="x">
> <query xmlns="jabber:iq:auth">...</query>
> </iq>
> 
> instead of something like:
> <iq type="set" id="x">
> <auth>...</auth>
> </iq>
> 
> Is there anyone out that who can shed light on the whys and hows of the protocol?
> 
> Thanks,
> Robert Temple
> 
> ___________________________________________________
> GO.com Mail                                    
> Get Your Free, Private E-mail at http://mail.go.com
> 
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20000831/f109b1b0/attachment-0002.pgp>