ecogrid returnfields need to support more xpath
When you are dealing with documents that store a lot of information in xml attributes instead of CDATA nodes, it is imperative that xpath attribute queries work correctly. AFAICT, they don't work at all with the ecogrid returnfields. For instance, the element:
<property name="semanticType000" class="org.kepler.sms.SemanticType"
The only meaniful way to get one of the attributes values based on another is via an attribute query like:
which should return the value attribute of any property node with a name attribute equal to 'semanticType000'.
#2 Updated by Chad Berkley over 14 years ago
this turns out to be a bigger issue than i thought. in face, i think it's a blocker for getting the remote actor search working in kepler. I had thought that, at least, the ecogrid would always return the returnfields in the same order which was allowing me to hack this by doing two returnfield queries then parsing the results (which were in effect name/value pairs). In fact, when i tried this on my laptop, the results were all hosed because the ecogrid returned the returnfields in totally different order than on my desktop. This has to be fixed soon.
Here's an example of the returnfields on my desktop with the query <returnfield>//property/@name</returnfield>
Note the values intuitively alternate. This makes sense to me. However, this is what I get when I do the same query on my laptop:
this is totally unparsable.