Solpadines,
The latest build of the engine squeaks because
<xsl:param name="operationID" select="'2'"/>
was removed at my request from service-
response.xsl.
I've put it back on sf with its default value
set to 999.
I've also put the default value of the
absoluteURL to the local host rather than socket.
Neither of these defaults should ever come into
play since we inject values each time, but the
top level param statements are needed.
I put a corrected stylesheet into the
gene_ontology service at:
http://socket.leeds.ac.uk/gene_ontology/consumer/
operation_list.html
If you submit toxin activity into operation 1
you see that the response is nearly there, but
not quite.
The property name and property values are a bit
mixed up.
The property name is missing in this xml
response (this is schema-valid).
In this case the property name should not appear
and the term Service response should appear in
the left-hand column of the table with the
actual text of the response in the right-hand
column.
When both the property name and property values
are present in the response, the property name
should appear in the left-hand column and the
value on the right.
So no string "Property Value" should ever appear
in the output.
Could you see to this, Rob, and let us know the
progress.
Regards,
Brian
|
