Lists Home |
Date Index |
> Personally I'd use qualified names rather than URIs for the "lookup",
> but that's because I envisage getting to annotation information
> through an axis rather than through a function and because QNames are
> easier to write than URIs. Perhaps a function:
> that returns a node set, and let the user use XPath mechanisms for
> doing the lookup within that node set?
This is fine in general, but I wonder what structure the node set would have.
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Apache 2.0 API - http://www-106.ibm.com/developerworks/linux/library/l-apache/
Python&XML column: Tour of Python/XML - http://www.xml.com/pub/a/2002/09/18/py.html
Python/Web Services column: xmlrpclib - http://www-106.ibm.com/developerworks/webservices/library/ws-pyth10.html