within ResourceSets and this is way too coarse grained. In fact I feel the concept of making ResourceSets the return value of XPath queries is a bad idea for a few reasons
1.) It is inconsistent with standard XPath. 2.) It is confusing to novice developers. 3.) Very rarely is a user simply interested in just the documents that match the query but in the actual nodes even for queries that return node lists. Let's try a relational database analogy... * Having queries return ResourceSets is like having all SQL queries return WHOLE tables and not rows or computed values. OK, how about an OODBMS analogy, * Having queries return ResourceSets is like having all SQL queries return WHOLE class instances and not fields or computed values. I think, however you slice it there needs to be a seperate class of objects returned by querys that are not as strongly related to Resources. -- THINGS TO DO IF I BECOME AN EVIL OVERLORD #44 I will only employ bounty hunters who work for money. Those who work for the pleasure of the hunt tend to do dumb things like even the odds to give the other guy a sporting chance. -- THINGS TO DO IF I BECOME AN EVIL OVERLORD #44 I will only employ bounty hunters who work for money. Those who work for the pleasure of the hunt tend to do dumb things like even the odds to give the other guy a sporting chance. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
