[standards-jig] UPDATED: JEP-0004

Thomas Muldowney temas at box5.net
Mon Sep 23 21:24:56 UTC 2002

> >You just broke all XPath parsers that want to treat fields the same.  
> >You can no longer just reach into a field and say XPath("field/value") 
> >and get back all of the values for the field.  Just to save you from 
> >having to look at a <value/> tag.  XML is designed to be structured, and 
> >often times structure interferes with ease of readability, but it sure 
> >lets the computer rip through things since it is orderly.
> Hmm, now _that_ is a better argument :)  Guess I have to ask how widely 
> XPath is used in the jabber community... in the work i've done so far, 
> it hasn't been worthwhile at all - forms processing has been pretty 
> straightforward and I can reach in and get the stuff I need directly, 
> without needing the power of XPath.  Would like to hear others' 
> experiences in this matter...

To reply specifically to the XPath stuff, many of the new clients are
heavily using XPath.  Exodus and Gabber2 I know off hand, and I have two
libraries in development that use XPath extensively.  The new
Net::Jabber also makes heavy (ok, _very_ heavy use of XPath) use.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20020923/648a4d48/attachment.sig>

More information about the Standards mailing list